Implement generalized sub routine find_in_log for tap test
vignesh C <vignesh21@gmail.com>
From: vignesh C <vignesh21@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-05-25T14:23:51Z
Lists: pgsql-hackers
Attachments
- 0001-Remove-duplicate-find_in_log-sub-routines-from-tap-t.patch (text/x-patch) patch 0001
Hi, The recovery tap test has 4 implementations of find_in_log sub routine for various uses, I felt we can generalize these and have a single function for the same. The attached patch is an attempt to have a generalized sub routine find_in_log which can be used by all of them. Thoughts? Regards, VIgnesh
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