Re: Postgres perl module namespace - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Postgres perl module namespace
Date
Msg-id 6790e47f-aa12-e28b-e123-3fbe46f78513@dunslane.net
Whole thread Raw
In response to Re: Postgres perl module namespace  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Postgres perl module namespace  (Michael Paquier <michael@paquier.xyz>)
Re: Postgres perl module namespace  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On 2022-04-19 Tu 18:39, Michael Paquier wrote:
> On Tue, Apr 19, 2022 at 04:06:28PM -0400, Andrew Dunstan wrote:
>> Here's a version with a fixed third patch that corrects a file misnaming
>> and fixes the export issue referred to above. Passes my testing so far.
> Wow.  That's really cool.  You are combining the best of both worlds
> here to ease backpatching, as far as I understand what you wrote.


Thanks.


>
> +*generate_ascii_string = *TestLib::generate_ascii_string;
> +*slurp_dir = *TestLib::slurp_dir;
> +*slurp_file = *TestLib::slurp_file;
>
> I am not sure if it is possible and my perl-fu is limited in this
> area, but could a failure be enforced when loading this path if a new
> routine added in TestLib.pm is forgotten in this list?



Not very easily that I'm aware of, but maybe some superior perl wizard
will know better.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Odd off-by-one dirty buffers and checkpoint buffers written
Next
From: Nathan Bossart
Date:
Subject: Re: Odd off-by-one dirty buffers and checkpoint buffers written