From: Ed L. <pgsql@bluepolka.net>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: pg_dump index creation order
Date: Sat, 6 May 2006 21:09:20 -0600
Message-ID: <200605062109.21084.pgsql@bluepolka.net> (raw)
In-Reply-To: <200605061915.55712.pgsql@bluepolka.net>
References: <200605061915.55712.pgsql@bluepolka.net>
On Saturday May 6 2006 7:15 pm, Ed L. wrote:
> I'm watching a long, painfully slow 60GB load from pg_dump
> (8.1.2), and noticing it's jumping back and forth from
> different tables. I assume this is the index creation order
> showing up.
>
> Would it make more sense to have pg_dump dump indexes grouped
> by the table? That way, if a table got loaded into cache for
> one index creation, it might still be there for the immediatly
> following index creations on the same table...
And would same idea work for ordering of constraint adding...?
Ed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@bluepolka.net
Subject: Re: pg_dump index creation order
In-Reply-To: <200605062109.21084.pgsql@bluepolka.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox