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: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Speeding up INSERTs and UPDATEs to partitioned tables |
Date: | 2018-11-01 01:30:55 |
Message-ID: | CAKJS1f8GDfvZotsQ4yyTBnKs1-oEjSJ-xMoq7edjL9WJ=qAX1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1 November 2018 at 13:35, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> On 2018/11/01 8:58, David Rowley wrote:
>> On 1 November 2018 at 06:45, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>> I think a better way to shorten the name would be to truncate the
>>> PartitionTupRouting() prefix in some way, e.g. dropping TupRouting.
>>
>> Thanks for chipping in on this.
>>
>> I agree. I don't think "TupRouting" really needs to be in the name.
>> Probably "To" can also just become "2" and we can put back the
>> Parent/Child before that.
>
> Agree that "TupRouting" can go, but "To" is not too long for using "2"
> instead of it.
Okay. Here's a version with "2" put back to "To"...
It's great to know the patch is now so perfect that we've only the
macro naming left to debate ;-)
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v12-0001-Speed-up-INSERT-and-UPDATE-on-partitioned-tables.patch | application/octet-stream | 64.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2018-11-01 01:40:31 | Re: Super PathKeys (Allowing sort order through precision loss functions) |
Previous Message | Michael Paquier | 2018-11-01 00:43:46 | Re: pg_promote not marked as parallel-restricted in pg_proc.dat |