Re: Making "COPY partitioned_table FROM" faster - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Making "COPY partitioned_table FROM" faster
Date
Msg-id d6546c1a-ce05-c589-f2f0-b5d9c964bee3@2ndquadrant.com
Whole thread Raw
In response to Re: Making "COPY partitioned_table FROM" faster  (David Rowley <david.rowley@2ndquadrant.com>)
Responses Re: Making "COPY partitioned_table FROM" faster
Re: Making "COPY partitioned_table FROM" faster
List pgsql-hackers
Two more thoughts:

- Add some tests.  The if (nBufferedTuples > 0) that flushes the tuples
when the partition changes is not currently exercised.

- With proute becoming a function-level variable,
cstate->partition_tuple_routing is obsolete and could be removed.  (No
point in saving this in cstate if it's only used in one function anyway.)

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Speeding up INSERTs and UPDATEs to partitioned tables
Next
From: Amit Langote
Date:
Subject: Re: Making "COPY partitioned_table FROM" faster