Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit980e887

Browse files
committed
Use higher wal_level for 004_io_direct.pl.
The new direct I/O test deliberately uses a very small shared_buffers toforce 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 buffersavailable" errors.We could presumably fix that by adjusting shared_buffers, but crakeseems 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
1 parent064750a commit980e887

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

‎src/test/modules/test_misc/t/004_io_direct.pl

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,7 @@
2323
'postgresql.conf',qq{
2424
io_direct = 'data,wal,wal_init'
2525
shared_buffers = '256kB' # tiny to force I/O
26+
wal_level = replica # minimal runs out of shared_buffers when set so tiny
2627
});
2728
$node->start;
2829

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp