Date: Fri, 15 Nov 2024 06:32:17 -0800
From: Noah Misch <noah@leadboat.com>
To: Christoph Berg <myon@debian.org>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>,
	Pavan Deolasee <pavan.deolasee@gmail.com>,
	pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Potential ABI breakage in upcoming minor releases
Message-ID: <20241115143217.43.nmisch@google.com>
References: <1976928.1731614974@sss.pgh.pa.us>
 <202411142033.u6za5a6ylj2k@alvherre.pgsql>
 <20241114224108.d0.nmisch@google.com>
 <ZzdQhiEfMYGpDleZ@msg.df7cb.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZzdQhiEfMYGpDleZ@msg.df7cb.de>
User-Agent: Mutt/2.2.12 (2023-09-09)
Archived-At: <https://www.postgresql.org/message-id/20241115143217.43.nmisch%40google.com>
Precedence: bulk

On Fri, Nov 15, 2024 at 02:45:42PM +0100, Christoph Berg wrote:
> Re: Noah Misch
> > I'm hearing the only confirmed impact on non-assert builds is the need to
> > recompile timescaledb.  (It's unknown whether recompiling will suffice for
> > timescaledb.  For assert builds, six PGXN extensions need recompilation.)
> 
> Which 6 extensions are these?
> 
> I re-ran the tests on all the extensions on apt.pg.o and didn't see
> any failures (timescale and age are already rebuilt).

I counted wrong, it's the five here:
https://postgr.es/m/20241114143524.91.nmisch@google.com

They are AGE and the four others you found not to be part of apt.pg.o.
(timescaledb is not part of PGXN, so it's not one of the five.)