Re: pg_dump versus hash partitioning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump versus hash partitioning
Date
Msg-id 1078804.1678504214@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump versus hash partitioning  (Julien Rouhaud <rjuju123@gmail.com>)
Responses Re: pg_dump versus hash partitioning  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
Julien Rouhaud <rjuju123@gmail.com> writes:
> Working on some side project that can cause dump of hash partitions to be
> routed to a different partition, I realized that --load-via-partition-root can
> indeed cause deadlock in such case without FK dependency or anything else.

> The problem is that each worker will perform a TRUNCATE TABLE ONLY followed by
> a copy of the original partition's data in a transaction, and that obviously
> will lead to deadlock if the original and locked partition and the restored
> partition are different.

Oh, interesting.  I wonder if we can rearrange things to avoid that.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: Lock mode in ExecMergeMatched()
Next
From: Amit Kapila
Date:
Subject: Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher