| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | "Kato, Sho" <kato-sho(at)jp(dot)fujitsu(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Performance improvements of INSERTs to a partitioned table |
| Date: | 2018-11-10 09:29:09 |
| Message-ID: | CAKJS1f9SepyZzmZrSCF8DBMtNvzouLYzbpeDULB4dZiG2BvVbw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9 November 2018 at 18:45, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> As long as queries involve tuple routing that touches multiple not yet
> seen partitions, someone doing conflicting operations directly on multiple
> partitions in a transaction will have to be ready to see deadlocks.
> Maybe, we can document that.
Perhaps it's good enough. A guess there's at least a workaround of
doing LOCK TABLE <root_partitioned_table> in the CREATE INDEX /
TRUNCATE session.
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Dent | 2018-11-10 10:14:50 | Re: Patch for Delta Materialized View Refreshes |
| Previous Message | Andres Freund | 2018-11-10 05:01:27 | Re: Skylake-S warning |