Re: Performance issue in pg_dump's dependency loop searching

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 17:43:47
Message-ID: CA+U5nM+2nU=bizBZqpUzVe9PCWcUNCVSxz6O6-M=darX8pS1kg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-07-29 18:06:30 Re: Performance issue in pg_dump's dependency loop searching
Previous Message Peter Geoghegan 2014-07-29 17:28:23 Re: Making joins involving ctid work for the benefit of UPSERT