Re: Implement generalized sub routine find_in_log for tap test
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Andrew Dunstan <andrew@dunslane.net>, Dagfinn Ilmari Mannsåker <ilmari@ilmari.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-06-09T02:59:03Z
Lists: pgsql-hackers
On Tue, Jun 06, 2023 at 05:53:40PM +0530, Bharath Rupireddy wrote: > Yes. A simpler way of doing it would be to move advance_wal() in > 019_replslot_limit.pl to Cluster.pm, something like the attached. CI > members don't complain with it > https://github.com/BRupireddy/postgres/tree/add_a_function_in_Cluster.pm_to_generate_WAL. > Perhaps, we can name it better instead of advance_wal, say > generate_wal or some other? Why not discussing that on a separate thread? What you are proposing is independent of what Vignesh has proposed. Note that the patch format is octet-stream, causing extra CRs to exist in the patch. Something happened on your side when you sent your patch, I guess? -- Michael
Commits
-
Refactor routine to find single log content pattern in TAP tests
- ced4cc30d5de 11.21 landed
- 3509a060d731 12.16 landed
- a9231fedae7a 13.12 landed
- 28af91b4e797 14.9 landed
- e25e5f7fc6b7 15.4 landed
- 392ea0c78fdb 16.0 landed
-
Refactor log check logic for connect_ok/fails in PostgreSQL::Test::Cluster
- 30469a6ed424 14.9 landed
- 7fa7911c7675 15.4 landed
- 26eaf82e7138 16.0 landed