Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uE8Tf-003TM8-II for pgsql-general@arkaria.postgresql.org; Sun, 11 May 2025 15:20:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uE8Td-00AQza-Bp for pgsql-general@arkaria.postgresql.org; Sun, 11 May 2025 15:20:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uE8Td-00AQzR-0c for pgsql-general@lists.postgresql.org; Sun, 11 May 2025 15:20:29 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uE8Ta-001Hcl-1m for pgsql-general@lists.postgresql.org; Sun, 11 May 2025 15:20:28 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 54BFKDbd892275; Sun, 11 May 2025 11:20:13 -0400 From: Tom Lane To: Achilleas Mantzios cc: "pgsql-general@lists.postgresql.org" , itdev@gatewaynet.com Subject: Re: Postgresql 18beta1 and SPI changes In-reply-to: <1e1e7585-4d72-4759-a49c-e58cd65be375@cloud.gatewaynet.com> References: <1e1e7585-4d72-4759-a49c-e58cd65be375@cloud.gatewaynet.com> Comments: In-reply-to Achilleas Mantzios message dated "Sun, 11 May 2025 18:04:38 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <892273.1746976813.1@sss.pgh.pa.us> Date: Sun, 11 May 2025 11:20:13 -0400 Message-ID: <892274.1746976813@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Achilleas Mantzios 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