Andrew Dunstan <and...@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
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
