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

From Alvaro Herrera
Subject Re: Potential ABI breakage in upcoming minor releases
Date
Msg-id 202411141629.3eavaz67xbmy@alvherre.pgsql
Whole thread Raw
In response to Potential ABI breakage in upcoming minor releases  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Responses Re: Potential ABI breakage in upcoming minor releases
List pgsql-hackers
Timescale at least has many users, I don't know about the others.  But
they won't be happy if we let things be.  IMO we should rewrap ...
especially 12, since there won't be a next one.

ISTM that we have spare bytes where we could place that boolean without
breaking ABI.  In x86_64 there's a couple of 4-byte holes, but those
won't be there on x86, so not great candidates.  Fortunately there are
3-byte and 7-byte holes also, which we can use safely.  We can move the
new boolean to those location.

The holes are different in each branch unfortunately.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"Use it up, wear it out, make it do, or do without"



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: Potential ABI breakage in upcoming minor releases
Next
From: Peter Geoghegan
Date:
Subject: Re: Potential ABI breakage in upcoming minor releases