Downloads
Home   >   mailing lists

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

From Dimitrios Apostolou
Subject Re: [PATCH] ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized
Date
Msg-id 4749eb1e-0fd6-f55b-034a-d3c0bbe5ba8b@gmx.net
Whole thread Raw
In response to [PATCH] ALTER TABLE ADD FOREIGN KEY to partitioned table, is not parallelized  (Dimitrios Apostolou <jimis@gmx.net>)
List pgsql-performance
Tree view 
>
> FWIW I implemented a pg_restore --freeze patch, see attached. It needs
> another patch of mine from [1] that implements pg_restore --data-only
> --clean, which for parallel restores encases each COPY in its own transaction
> and prepends it with a TRUNCATE. All feedback is welcome.
>
> [1] https://www.postgresql.org/message-id/c61263f2-7472-5dd8-703d-01e683421f61%40gmx.net
>
> It works really fast for the data, and I see that some, but not all items
> from section=post-data, start parallel plans. For example I see CREATE INDEX
> spawns parallel workers.

I added it to July's commitfest, mostly to trigger discussion around the
issue.

https://commitfest.postgresql.org/patch/5826/

Not sure how to mark on the commitfest page that the patch requires
another patch from another commitfest entry.


Dimitris

pgsql-performance by date:

Previous
From: Dimitrios Apostolou
Date:
Subject: Re: Performance implications of 8K pread()s
Next
From: James Pang
Date:
Subject: many deletes and inserts on pg_class, total rows is 14200 rows in "pg_class", any idea why so many inserts/deletes on "pg_class" it's self?