Re: Query execution in Perl TAP tests needs work
От | Andrew Dunstan |
---|---|
Тема | Re: Query execution in Perl TAP tests needs work |
Дата | |
Msg-id | fc617e2e-f171-46fc-faf9-b4c5ce54c735@dunslane.net обсуждение исходный текст |
Ответ на | Re: Query execution in Perl TAP tests needs work (Thomas Munro <thomas.munro@gmail.com>) |
Список | pgsql-hackers |
On 2023-09-02 Sa 20:17, Thomas Munro wrote:
On Sun, Sep 3, 2023 at 6:42 AM Andrew Dunstan <andrew@dunslane.net> wrote:I confess I'm a little reluctant to impose this burden on buildfarm owners. We should think about some sort of fallback in case this isn't supported on some platform, either due to technological barriers or buildfarm owner reluctance.I guess you're thinking that it could be done in such a way that it is automatically used for $node->safe_psql() and various other things if Platypus is detected, but otherwise forking psql as now, for a transition period? Then we could nag build farm owners, and eventually turn off the fallback stuff after N months. After that it would begin to be possible to use this in more interesting and advanced ways.
Yeah, that would be ideal. I'll prep a version of the module that doesn't fail if FFI::Platypus isn't available, but instead sets a flag we can test.
cheers
andrew
-- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: