| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, amul sul <sulamul(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
| Subject: | Re: [HACKERS] Runtime Partition Pruning |
| Date: | 2018-04-13 05:48:42 |
| Message-ID: | 9144632f-d1e8-258a-567f-86e156e07731@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2018/04/13 14:38, Amit Langote wrote:
> About the specific relation_open(.., NoLock) under question, I think there
> might be a way to address this by opening the tables with the appropriate
> lock mode in partitioned_rels list in ExecLockNonleafAppendTables
That may have sounded a bit confusing:
I meant to say: "by opening the tables in partitioned_rels list with the
appropriate lock mode in ExecLockNonleafAppendTables"
> Attached a PoC patch.
There were a couple of unnecessary hunks, which removed in the attached.
Thanks,
Amit
| Attachment | Content-Type | Size |
|---|---|---|
| open-partitioned-rels-for-pruning-2.patch | text/plain | 9.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2018-04-13 05:58:34 | Re: [HACKERS] Runtime Partition Pruning |
| Previous Message | Amit Langote | 2018-04-13 05:38:46 | Re: [HACKERS] Runtime Partition Pruning |