On 2015-07-08 10:58:51 -0300, Fabrízio de Royes Mello wrote: > Think in an ETL job that can be use an unlogged table to improve the load > performance, but this job create a "large table" and to guarantee the data > consistency you need to transform it into a regular table, and with the > current implementation rewrite the entire heap, toast and indexes.
Don't buy that. The final target relation will usually already have content. Also everything but wal_level=minimal will force you to WAL log the contents anyway. -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
