pgsql: Use higher wal_level for 004_io_direct.pl.

From: Thomas Munro <tmunro(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Use higher wal_level for 004_io_direct.pl.
Date: 2023-04-08 20:36:46
Message-ID: E1plFIj-0026Ce-5K@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(at)anarazel(dot)de>
Discussion: https://postgr.es/m/20230408060408.n7xdwk3mxj5oykt6%40awork3.anarazel.de

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/980e8879f54a7a00ca6a5bae2fe9486c87ef3e8e

Modified Files
--------------
src/test/modules/test_misc/t/004_io_direct.pl | 1 +
1 file changed, 1 insertion(+)

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2023-04-08 20:37:04 Re: pgsql: Skip \password TAP test on old IPC::Run versions
Previous Message Tom Lane 2023-04-08 20:30:00 Re: pgsql: Skip \password TAP test on old IPC::Run versions