Re: Delay locking partitions during INSERT and UPDATE - Mailing list pgsql-hackers

From David Rowley
Subject Re: Delay locking partitions during INSERT and UPDATE
Date
Msg-id CAKJS1f8A5XLEGHYQkVy+PFsqKRODKZrCAM5_S9fZyGYhqL9Uow@mail.gmail.com
Whole thread Raw
In response to Re: Delay locking partitions during INSERT and UPDATE  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Delay locking partitions during INSERT and UPDATE  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Sat, 2 Feb 2019 at 03:07, Robert Haas <robertmhaas@gmail.com> wrote:
> I'm now wondering whether the same issues discussed in
> https://www.postgresql.org/message-id/CA%2BTgmoZN-80143F8OhN8Cn5-uDae5miLYVwMapAuc%2B7%2BZ7pyNg%40mail.gmail.com
> also need discussion with respect to this patch.  But I haven't
> thought about it very hard, so I'm not sure whether they do or don't.

I really don't think it does, or if it does then the code is already
broken as it is now.

As the code is today, we obtain the locks well after the plan is
locked in.  The only difference with this patch is that we do the
locking on routing tuples to the partition for the first time rather
than do them all at once when setting up the routing data structure.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: speeding up planning with partitions
Next
From: Tom Lane
Date:
Subject: Re: LD_LIBRARY_PATH_RPATH