From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
---|---|
To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
Subject: | Re: Interrupts vs signals |
Date: | 2024-11-10 21:30:13 |
Message-ID: | 3311387e-08b3-429d-b339-13fda075682b@iki.fi |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/11/2024 22:21, Jelte Fennema-Nio wrote:
> On Mon, 4 Nov 2024 at 20:42, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
>> Having spent some time playing with this, I quite like option C: break
>> compatibility, but provide an out-of-tree header file with
>> *forward*-compatibility macros. That encourages extension authors to
>> adapt to new idioms, but avoids having to sprinkle extension code with
>> #if version checks to support old versions.
>
> +1 maintaining a subset of these things for every extension is kind of a pain
>
>> My plan is to put this on the Wiki
>
> Why the wiki and not as a file in the repo? Seems like it would be
> nice to update this file together with patches that introduce such
> breakages. To be clear, I think it shouldn't be possible to #include
> the file, such a forward compatibility file should always be
> copy-pasted. But having it in the same place as the code seems useful,
> just like we update docs together with the code.
I thought of the Wiki so that it could updated more casually by
extension authors. But sure, it could be a file in the main repo too.
--
Heikki Linnakangas
Neon (https://neon.tech)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-11-10 21:37:12 | Re: [BUG] psql: Make \copy from 'text' and 'csv' formats fail on NUL bytes |
Previous Message | Joel Jacobson | 2024-11-10 21:26:20 | [BUG] psql: Make \copy from 'text' and 'csv' formats fail on NUL bytes |