| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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 23:30:17 |
| Message-ID: | CAKJS1f9BfyRnAFU7KAp8R+FAADFyjgag3vNf6X5if4xo087gqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 19 Feb 2019 at 12:15, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> > Looks like you're looking at the patch from the "Delay locking
> > partitions during query execution" thread [1]. Different thing
> > altogether, although the names are confusingly similar.
>
> My apologies --- I searched my inbox for "Delay locking partitions",
> and failed to notice that I was extracting a patch from the wrong
> thread with that in its title. (The questions I posed should
> be posted to that thread instead, as they still apply there.)
Easily done. Happy to answer the question there if you ask it there.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-02-18 23:42:32 | Re: Speed up transaction completion faster after many relations are accessed in a transaction |
| Previous Message | David Rowley | 2019-02-18 23:28:32 | Re: Delay locking partitions during INSERT and UPDATE |