On Tue, Jul 29, 2014 at 3:06 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Simon Riggs <si...@2ndquadrant.com> writes: >> On 25 July 2014 20:47, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> Another idea would be to > >> ...persist the optimal dump order in the database. > >> That way we can maintain the correct dump order each time we do DDL, >> which is only a small incremental cost, no matter how many objects we >> have. > > I don't see any obvious way to make it incremental; so I doubt that > it would be a small extra cost. In any case I disagree that making DDL > slower to make pg_dump faster is a good tradeoff. Many people seldom > or never use pg_dump. > > regards, tom lane
Not to mention slowing down temp tables -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers