Re: concurrent COPY performance - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: concurrent COPY performance
Date
Msg-id 4A37D2F90200002500027C39@gw.wicourts.gov
Whole thread Raw
In response to Re: concurrent COPY performance  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: concurrent COPY performance  (Gurjeet Singh <singh.gurjeet@gmail.com>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> wrote:
> If a table is created or truncated in the same transaction that does
> the load, and archiving is not on, the COPY is not WALed.
Slightly off topic, but possibly relevant to the overall process:
those are the same conditions under which I would love to see the
rows inserted with the hint bits showing successful commit and the
transaction ID showing frozen.  We currently do a VACUUM FREEZE
ANALYZE after such a load, to avoid burdening random users with the
writes.  It would be nice not to have to write all the pages again
right after a load.
-Kevin


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: concurrent COPY performance
Next
From: Stefan Kaltenbrunner
Date:
Subject: Re: concurrent COPY performance