| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | 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 04:47:26 |
| Message-ID: | 1239149.1600145246@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2020-Sep-14, Tom Lane wrote:
>> AFAICS, it is utterly silly for InitResultRelInfo to be forcing
>> a partition qual to be computed when we might not need it.
>> We could flush ResultRelInfo.ri_PartitionCheck altogether and
>> have anything that was reading it instead do
>> RelationGetPartitionQual(ResultRelInfo.ri_RelationDesc).
> Hmm, but I presume we don't want to compute it every time. I suggest we
> would still have it, but we'd only computed it when first used.
RelationGetPartitionQual already does that caching.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-09-15 04:47:41 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | Bharath Rupireddy | 2020-09-15 04:41:00 | Re: Parallelize stream replication process |