| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | 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-01 14:07:37 |
| Message-ID: | CA+TgmobmyrBM_ck=KXOMLv9VWzi4-Gjn3Lbu+L3M+KkDzo6jQQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 31, 2019 at 4:48 PM David Rowley
<david(dot)rowley(at)2ndquadrant(dot)com> wrote:
> On Fri, 1 Feb 2019 at 07:46, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > I have reviewed this patch and I am in favor of it. I think it likely
> > needs minor rebasing because of the heap_open -> table_open renaming.
>
> Many thanks for looking at it. The v2 patch was based on top of the
> heap_open -> table_open change.
Oops. I guess I opened the wrong version.
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2019-02-01 14:09:41 | Re: speeding up planning with partitions |
| Previous Message | Robert Haas | 2019-02-01 14:00:36 | Re: ATTACH/DETACH PARTITION CONCURRENTLY |