aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_utilcmd.c
diff options
context:
space:
mode:
authorThomas Munro <tmunro@postgresql.org>2023-04-09 08:27:36 +1200
committerThomas Munro <tmunro@postgresql.org>2023-04-09 08:27:36 +1200
commit980e8879f54a7a00ca6a5bae2fe9486c87ef3e8e (patch)
treed25513128369141dddd444afcec0def5c1823409 /src/backend/parser/parse_utilcmd.c
parent064750af4f4ebab9c0d47d502c7ff7e3c9533f9f (diff)
downloadpostgresql-980e8879f54a7a00ca6a5bae2fe9486c87ef3e8e.tar.gz
postgresql-980e8879f54a7a00ca6a5bae2fe9486c87ef3e8e.zip
Use higher wal_level for 004_io_direct.pl.
The new direct I/O test deliberately uses a very small shared_buffers to force some disk transfers without making the data set large and slow, but ran into a problem with wal_level = minimal: log_newpage_range() pins many buffers, leading to a few intermittent "no unpinned buffers available" errors. We could presumably fix that by adjusting shared_buffers, but crake seems to be trying to tell us something interesting with these settings, so let's just avoid wal_level = minimal in this test for now. Reported-by: Andres Freund <andres@anarazel.de> Discussion: https://postgr.es/m/20230408060408.n7xdwk3mxj5oykt6%40awork3.anarazel.de
Diffstat (limited to 'src/backend/parser/parse_utilcmd.c')
0 files changed, 0 insertions, 0 deletions