On Wed, Jul 8, 2015 at 10:53 AM, Andres Freund <and...@anarazel.de> wrote: > > On 2015-07-03 08:18:09 -0300, Fabrízio de Royes Mello wrote: > > *** ALTER TABLE changes > > ... > > Without going into the specifics of this change: Are we actually sure > this feature warrants the complexity it'll introduce? I'm really rather > doubtful.
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. Regards, -- Fabrízio de Royes Mello Consultoria/Coaching PostgreSQL >> Timbira: http://www.timbira.com.br >> Blog: http://fabriziomello.github.io >> Linkedin: http://br.linkedin.com/in/fabriziomello >> Twitter: http://twitter.com/fabriziomello >> Github: http://github.com/fabriziomello
