Re: Why do we have perl and sed versions of Gen_dummy_probes? - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Why do we have perl and sed versions of Gen_dummy_probes?
Date
Msg-id 2310ae84-547c-9e5e-4d2c-c221ed1a7dc9@dunslane.net
Whole thread Raw
In response to Re: Why do we have perl and sed versions of Gen_dummy_probes?  (Andres Freund <andres@anarazel.de>)
Responses Re: Why do we have perl and sed versions of Gen_dummy_probes?
List pgsql-hackers
On 5/6/21 12:59 AM, Andres Freund wrote:
> Hi,
>
> On 2021-05-06 00:18:12 -0400, Tom Lane wrote:
>> Andres Freund <andres@anarazel.de> writes:
>>> I understand why we don't want to rely on sed because of windows - but
>>> it's far from obvious why we can't just use the .pl variant all the
>>> time?
>> Perl is not considered a hard build requirement on non-Windows.
> Oops, forgot that.
>
>
>> We could dodge that by shipping a pre-built dummy probes.h,
>> but that doesn't really seem like a cleaner way than what's
>> there now.
> I tried to regenerate Gen_dummy_probes.pl using s2p - which doesn't seem
> to exist for modern versions of perl anymore :(
>
>
>> Also, as I read it, Gen_dummy_probes.sed is useful in any case as
>> being the "source code" for Gen_dummy_probes.pl.  You'd need some
>> other form of documentation if you removed it.


I suggest we add a README that sets out


a) why we do things this way

b) that the sed script is what's authoritative

c) how to regenerate the perl script if you change the sed script,
including where to get s2p


I can do that.


cheers


andrew


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




pgsql-hackers by date:

Previous
From: Dilip Kumar
Date:
Subject: Re: Toast compression method options
Next
From: Nitin Jadhav
Date:
Subject: Multi-Column List Partitioning