NotificationsYou must be signed in to change notification settings
Fork6
Star31

Commit4964253

committed

Put back explicit setting of replication values within TAP tests.

Commit151c0c5 neglected the possibility that a TEMP_CONFIG filewould explicitly set max_wal_senders=0; as indeed buildfarm memberthorntail does, so that it can test wal_level=minimal in other testsuites. Hence, rather than assuming that max_wal_senders=10 willprevail if we say nothing, set it explicitly.Set max_replication_slots=10 explicitly too, just to be safe.Back-patch to v10, like the previous patch.Discussion:https://postgr.es/m/723911.1601417626@sss.pgh.pa.us

1 parente176187 commit4964253Copy full SHA for 4964253

File tree

1 file changed

-1

lines changed

src/test/perl
- PostgresNode.pm

1 file changed

-1

lines changed

`‎src/test/perl/PostgresNode.pm`

Lines changed: 4 additions & 1 deletion

Original file line number	Diff line number	Diff line change
`@@ -469,12 +469,15 @@ sub init`
`469`	`469`	`{`
`470`	`470`	`print$conf"wal_level = replica\n";`
`471`	`471`	`}`
`472`		`-print$conf"max_wal_size = 128MB\n";`
	`472`	`+print$conf"max_wal_senders = 10\n";`
	`473`	`+print$conf"max_replication_slots = 10\n";`
`473`	`474`	`print$conf"wal_log_hints = on\n";`
`474`	`475`	`print$conf"hot_standby = on\n";`
`475`	`476`	`# conservative settings to ensure we can run multiple postmasters:`
`476`	`477`	`print$conf"shared_buffers = 1MB\n";`
`477`	`478`	`print$conf"max_connections = 10\n";`
	`479`	`+# limit disk space consumption, too:`
	`480`	`+print$conf"max_wal_size = 128MB\n";`
`478`	`481`	`}`
`479`	`482`	`else`
`480`	`483`	`{`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

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

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit4964253

File tree

1 file changed

1 file changed

`‎src/test/perl/PostgresNode.pm`

0 commit comments