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 a56db2e7-fbcd-fc43-8158-c6c2dde36f35@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  (Melanie Plageman <melanieplageman@gmail.com>)
Re: Making "COPY partitioned_table FROM" faster  (David Rowley <david.rowley@2ndquadrant.com>)
List pgsql-hackers
On 30/07/2018 15:26, David Rowley wrote:
>> - Add some tests.  The if (nBufferedTuples > 0) that flushes the tuples
>> when the partition changes is not currently exercised.
> 
> That seems like a good idea. In fact, it uncovered a bug around
> ConvertPartitionTupleSlot() freeing the previously stored tuple out
> the slot which resulted in a crash. I didn't notice before because my
> test had previously not required any tuple conversions.

I think we need to think of a better place to put that temporary file,
and clean it up properly afterwards.  I'm not sure whether we have
existing uses like that.

Also, maybe the test should check afterwards that the right count of
rows ended up in each partition?

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


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: Adding a note to protocol.sgml regarding CopyData
Next
From: Andres Freund
Date:
Subject: Re: Expression errors with "FOR UPDATE" and postgres_fdw withpartition wise join enabled.