Re: Speeding up INSERTs and UPDATEs to partitioned tables - Mailing list pgsql-hackers

From David Rowley
Subject Re: Speeding up INSERTs and UPDATEs to partitioned tables
Date
Msg-id CAKJS1f81q2yztfgEnUYN89h44-z2_pk8GuPiqp1vNG_fvyYzog@mail.gmail.com
Whole thread Raw
In response to Re: Speeding up INSERTs and UPDATEs to partitioned tables  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
Responses Re: Speeding up INSERTs and UPDATEs to partitioned tables  (Jesper Pedersen <jesper.pedersen@redhat.com>)
Re: Speeding up INSERTs and UPDATEs to partitioned tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On 9 November 2018 at 19:18, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp> wrote:
> I have a comment regarding how you chose to make
> PartitionTupleRouting private.
>
> Using the v14_to_v15 diff, I could quickly see that there are many diffs
> changing PartitionTupleRouting to struct PartitionTupleRouting, but they
> would be unnecessary if you had added the following in execPartition.h, as
> my upthread had done.
>
> -/* See execPartition.c for the definition. */
> +/* See execPartition.c for the definitions. */
>  typedef struct PartitionDispatchData *PartitionDispatch;
> +typedef struct PartitionTupleRouting PartitionTupleRouting;

Okay, done that way. v16 attached.

The 0002 patch is included again, this time with a new proposed commit
message.  There was some discussion over on [1] where nobody seemed to
have any concerns about delaying the locking until we route the first
tuple to the partition.

[1] https://www.postgresql.org/message-id/25C1C6B2E7BE044889E4FE8643A58BA963B5796B@G01JPEXMBKW03

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Bug Fix]ECPG: cancellation of significant digits on ECPG
Next
From: Peter Eisentraut
Date:
Subject: Re: Support custom socket directory in pg_upgrade