| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Delay locking partitions during INSERT and UPDATE |
| Date: | 2019-02-18 22:53:27 |
| Message-ID: | 20190218225327.zmoabpw5ydqz3tei@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2019-02-18 17:47:07 -0500, Tom Lane wrote:
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> > Not sure what you mean here. This is an executor change. What does
> > the planner care about what the executor does?
>
> Are we talking about the same patch? The one I'm looking at seems
> to be mostly planner and plancache changes:
I think so - the patch in this thread is much simpler:
diffstat < /tmp/v2-0001-Delay-locking-of-partitions-during-INSERT-and-UPD.patch
execPartition.c | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)
that's the patch upthread from here, at
https://www.postgresql.org/message-id/CAKJS1f_hWSiC9j9HkZCfNVQs-bbHY-P2RqbH4bYcEHmWtpyLRw%40mail.gmail.com
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-02-18 22:56:22 | Re: Delay locking partitions during INSERT and UPDATE |
| Previous Message | Andrew Dunstan | 2019-02-18 22:50:20 | Re: Missing Column names with multi-insert |