Re: Potential ABI breakage in upcoming minor releases - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Potential ABI breakage in upcoming minor releases
Date
Msg-id 20241204210056.df.nmisch@google.com
Whole thread Raw
In response to Re: Potential ABI breakage in upcoming minor releases  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Dec 04, 2024 at 08:29:57PM +0100, Peter Eisentraut wrote:
> On 29.11.24 21:39, Noah Misch wrote:
> > > I remembered where that's documented:
> > > 
> > > https://wiki.postgresql.org/wiki/Committing_checklist#Maintaining_ABI_compatibility_while_backpatching
> > I'd say the source tree's <sect2 id="xfunc-api-abi-stability-guidance">, which
> > David Wheeler mentioned, is authoritative.  It currently matches
> > postgr.es/c/e54a42a.  Let's update both or change that wiki heading to point
> > to the authoritative doc section.

I hereby revoke the last sentence and replace it with "Let's update both in
some way."  The revoked sentence and its replacement are probably the least
important thing I wrote in that mail.

> I don't know if this proposing to merge the text in the wiki into the docs?

The revoked proposal wasn't that specific.  1576843.1732586210@sss.pgh.pa.us
offered some wiki changes mostly about struct fields.  Doc section
xfunc-api-abi-stability-guidance also writes about struct fields.
Specifically, it discusses "squeezing a new field into padding space or
appending it to the end of a struct".  If we change the wiki about struct
fields, we should not leave that quote unchanged.  I no longer wish to affect
how we allocate text to the wiki vs. xfunc-api-abi-stability-guidance.



pgsql-hackers by date:

Previous
From: Sergey Prokhorenko
Date:
Subject: Benchmark function for uuidv7()
Next
From: Thomas Munro
Date:
Subject: Re: Cannot find a working 64-bit integer type on Illumos