Feedback-ID: i76984098:Fastmail
Message-ID: <d3f6426f-ef55-407d-918d-20d59c6a2c26@aklaver.com>
Date: Tue, 19 Nov 2024 08:17:16 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: PostgreSQL 15.9 Update: Partitioned tables with foreign key
 constraints
To: Paul Foerster <paul.foerster@gmail.com>,
 pgsql-general list <pgsql-general@lists.postgresql.org>
References: <A1FAF798-A5DB-4C44-904E-AB2675A838BF@gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <A1FAF798-A5DB-4C44-904E-AB2675A838BF@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/d3f6426f-ef55-407d-918d-20d59c6a2c26%40aklaver.com>
Precedence: bulk

On 11/19/24 08:11, Paul Foerster wrote:
> Hi,
> 
> the PostgreSQL 15.9 release notes instruct to look out for especially detached partitions with foreign key constraints. I'm in the process of updating our databases from 15.8 to 15.9 now and found a case where the select statement returns a constraint.
> 
> The release notes say nothing about when to fix that using the generated add or drop statements.
> 
> Do I want/need to do that before or after I exchange the software? And if it is to be done on a particular of the two releases, why is that?
> 
> https://www.postgresql.org/docs/15/release-15-9.html
> Section E.1.2, changelog entry 5.
> 
> Any insight would be highly appreciated. Thanks in advance.

Read this:

https://www.postgresql.org/about/news/out-of-cycle-release-scheduled-for-november-21-2024-2958/

and hold off awhile.

> 
> Cheers
> Paul
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com