Re: Performance issue in pg_dump's dependency loop searching

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Joe Van Dyk <joe(at)tanga(dot)com>
Subject: Re: Performance issue in pg_dump's dependency loop searching
Date: 2014-07-29 18:06:30
Message-ID: 4653.1406657190@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> On 25 July 2014 20:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2014-07-29 18:28:02 Re: Performance issue in pg_dump's dependency loop searching
Previous Message Simon Riggs 2014-07-29 17:43:47 Re: Performance issue in pg_dump's dependency loop searching