Postgres Pro
Downloads
Home   >   mailing lists

Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized - Mailing list pgsql-performance

From Frédéric Yhuel
Subject Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized
Date
Msg-id 90e55c6b-3d79-4bf8-8874-a64dd10a0286@dalibo.com
Whole thread Raw
In response to Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized  (Dimitrios Apostolou <jimis@gmx.net>)
Responses Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized
List pgsql-performance
Tree view 

On 6/4/25 16:12, Dimitrios Apostolou wrote:
> In general I have noticed most operations are slower after a succesful 
> pg_restore until VACUUM is complete, which is unfortunate as the 
> database is huge and it takes days to run. Something I have on my list 
> to try, is whether a COPY FREEZE would alleviate all this trouble, since 
> all tuples are immediately visible then. Maybe a patch for a new 
> pg_restore option --freeze is a better solution. Are my assumptions right?

It seems that the idea has already been discussed: 

https://www.postgresql.org/message-id/flat/CA%2BU5nM%2BXvkUu9ran%2B5cY%3DTWQquLTpvzte4KVMK%3DaDfbr-xfNXA%40mail.gmail.com#b61a7fee06e10e61afa68712bc0b3c5b

I've CCed Bruce Mojman, in the hope that he can tell us more about it.

pgsql-performance by date:

Previous
From: Dimitrios Apostolou
Date:
Subject: Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized
Next
From: Frédéric Yhuel
Date:
Subject: Re: ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized