Re: Query execution in Perl TAP tests needs work - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Query execution in Perl TAP tests needs work
Date
Msg-id CA+hUKGKyubv1Jq+qC7eyE+2GE3jootRMX0TdGU7PvyhejFQ_Xw@mail.gmail.com
Whole thread Raw
In response to Re: Query execution in Perl TAP tests needs work  (Andrew Dunstan <andrew@dunslane.net>)
List 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
atthe 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?



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Query execution in Perl TAP tests needs work
Next
From: vignesh C
Date:
Subject: Re: persist logical slots to disk during shutdown checkpoint