Re: pg_upgrade slowness for databases with many tables - Mailing list pgsql-bugs

From Tom Lane
Subject Re: pg_upgrade slowness for databases with many tables
Date
Msg-id 26756.1432479774@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade slowness for databases with many tables  (Stefan Seifert <nine@detonation.org>)
List pgsql-bugs
Stefan Seifert <nine@detonation.org> writes:
> It looks like LockReassignCurrentOwner is taking most of the time.

Yeah, so that is the issue that was alleviated by the patch you were
pointed to.

> What I really wonder though is, why pg_dump does all these queries for single
> objects in the first place? If the target is to create a complete schema dump,
> why not doing a select * from all the relevant pg_* tables and construct the
> big picture in memory? That surely would be much faster?

It's unclear that it would be faster, and it is clear that restructuring
pg_dump like that would be a lotta work.

            regards, tom lane

pgsql-bugs by date:

Previous
From: kou@clear-code.com
Date:
Subject: BUG #13343: Yum repository URL for RHEL 6.7 i386 has needless "."
Next
From: Michael Paquier
Date:
Subject: Incorrect processing of CREATE TRANSFORM with DDL deparding