Re: Postgresql 18beta1 and SPI changes

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
Cc: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>, itdev@gatewaynet.com
Date: 2025-05-11T15:20:13Z
Lists: pgsql-general
Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com> writes:
> We use are own version of DBmirror, we run our replication in a highly 
> fine grained manner. So every upgrade I have to make the code compile 
> and test. Up to PostgreSQL 17, I only got minor compilation problems 
> that I managed to resolve fairly easily. However this didn't prove to be 
> the case with PostgreSQL 18beta1, it proved harder to compile and as my 
> fears were verified, it has serious problems.

> My question : is 18's SPI stabilized ? Can I start work on our version 
> of DBmirror ? Or wait for 18beta2 or -RC ?

If you think there are changes we need to make, you'd better get
specific sooner not later.  I'm not aware of any large fixes that
are pending, cf

https://wiki.postgresql.org/wiki/PostgreSQL_18_Open_Items

			regards, tom lane



Commits

  1. Introduce CompactAttribute array in TupleDesc