| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Domagoj Smoljanovic <domagoj(dot)smoljanovic(at)oradian(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_restore causing deadlocks on partitioned tables |
| Date: | 2020-09-15 14:15:12 |
| Message-ID: | 1288760.1600179312@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Amit Langote <amitlangote09(at)gmail(dot)com> writes:
> On Tue, Sep 15, 2020 at 10:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Ah, right. That seems like a bug but we have not attempted to fix it.
> IIRC, when this behavior was brought up as a bug in past discussions,
> it was decided that it will be fixed when NOT NULL constraints are
> represented using pg_constraint entries.
Yeah, that matches my recollection too.
>> But we could restrict the optimization to partitioned tables, where
>> the assumption does hold, no?
> Yeah, seems safe in their case.
And that's sufficient to cover pg_restore's issue, since it's
only going to be trying to do this for partitioned tables.
I'll wait till tomorrow to push this, since we're still in
freeze mode for the v13 branch.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-09-15 14:59:39 | Re: PG 13 release notes, first draft |
| Previous Message | Jakub Wartak | 2020-09-15 14:10:24 | Re: Optimising compactify_tuples() |