Re: Delay locking partitions during INSERT and UPDATE
Tomas Vondra <tomas.vondra@2ndquadrant.com>
From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: John Naylor <john.naylor@2ndquadrant.com>
Cc: David Rowley <david.rowley@2ndquadrant.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-01-24T21:42:55Z
Lists: pgsql-hackers
On 1/24/19 10:34 PM, John Naylor wrote: > On Thu, Jan 24, 2019 at 4:17 PM Tomas Vondra > <tomas.vondra@2ndquadrant.com> wrote: >> I can still see about the same performance as before (on both clusters). > > Thanks for checking! I think the thing to do now is have a committer > look at it. It's a small patch with obvious performance effects -- > there's just the question of whether the locking behavior with > concurrent DDL is as safe as it is now. > > Anyone have anything else? > Yes, I don't see why would the patch change that and I've been looking for such cases. I think David was looking at that this week too, and I assume he'll send an update if he finds anything. If not, I plan to get it committed soon-ish (possibly next week after the FOSDEM dev meeting, unless there are some objections). regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Delay lock acquisition for partitions until we route a tuple to them.
- 9eefba181f77 12.0 landed