Re: Query execution in Perl TAP tests needs work
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-08-29T04:33:48Z
Lists: pgsql-hackers
On Tue, Aug 29, 2023 at 1:23 AM Andrew Dunstan <andrew@dunslane.net> wrote: > I like the idea of using a pure perl pq implementation, not least because it could expand our ability to test things at the protocol level. Not sure how much work it would be. I'm willing to help if we want to go that way. Cool. Let's see what others think. And assuming we can pick *something* vaguely efficient and find a Perl hacker to implement it, a related question is how to expose it to our test suites. Should we figure out how to leave all our tests unchanged, by teaching $node->psql() et al to do caching implicitly? Or should we make it explicit, with $conn = $node->connect(), and $conn->do_stuff()? And if the latter, should do_stuff be DBI style or something that suits us better?
Commits
-
Backport IPC::Run optimization to src/test/perl.
- 06558f495295 17.0 landed
-
perl5 interface moved to gborg
- 9a0b4d7f8474 7.3.1 cited