Re: Potential ABI breakage in upcoming minor releases

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Marco Slot <marco(dot)slot(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Christoph Berg <myon(at)debian(dot)org>, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
Subject: Re: Potential ABI breakage in upcoming minor releases
Date: 2024-11-15 18:24:35
Message-ID: A8F51466-0039-47E9-A29C-E5917CB604F4@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Nov 15, 2024, at 12:52, Noah Misch <noah(at)leadboat(dot)com> wrote:

> Either way, users of timescaledb should rebuild timescaledb for every future
> PostgreSQL minor release.

Ugh, was really hoping to get to a place where we could avoid requiring rebuilds of any extension for every minor release. :-( We even added ABI guidance to the docs[1] about this.

Best,

David

[1]: https://commitfest.postgresql.org/48/5080/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2024-11-15 18:35:29 Re: Potential ABI breakage in upcoming minor releases
Previous Message Tomas Vondra 2024-11-15 18:21:05 Re: logical replication: restart_lsn can go backwards (and more), seems broken since 9.4