| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Potential ABI breakage in upcoming minor releases |
| Date: | 2024-11-14 16:29:34 |
| Message-ID: | 202411141629.3eavaz67xbmy@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-11-14 16:35:25 | Re: Potential ABI breakage in upcoming minor releases |
| Previous Message | Christoph Berg | 2024-11-14 16:29:18 | Re: Potential ABI breakage in upcoming minor releases |