Re: Performance issue in pg_dump's dependency loop searching - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Performance issue in pg_dump's dependency loop searching
Date
Msg-id CAGTBQpa1fjDiJd323Xq-HFOo3VqSyGG+=pY7Bp_H=kZToSBo8w@mail.gmail.com
Whole thread Raw
In response to Re: Performance issue in pg_dump's dependency loop searching  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Jul 29, 2014 at 3:06 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> On 25 July 2014 20:47, Tom Lane <tgl@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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Performance issue in pg_dump's dependency loop searching
Next
From: Peter Geoghegan
Date:
Subject: Re: B-Tree support function number 3 (strxfrm() optimization)