From: Tom Lane <tgl@sss.pgh.pa.us>
To: Campbell, Lance <lance@illinois.edu>
Cc: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Re: pg_restore new parameter request
Date: Mon, 23 Nov 2015 09:50:13 -0500
Message-ID: <1825.1448290213@sss.pgh.pa.us> (raw)
In-Reply-To: <B75CD08C73BD3543B97E4EF3964B7D702015E9C6@CHIMBX1.ad.uillinois.edu>
References: <B75CD08C73BD3543B97E4EF3964B7D702015E9C6@CHIMBX1.ad.uillinois.edu>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
"Campbell, Lance" <lance@illinois.edu> writes:
> PostgreSQL pg_restore new feature request
> I did some testing last week to see how fast I could get pg_restore to reload data. I found some settings that made a significant speed boost. One request I have is the addition of two parameters to pg_restore.
> --no-indexes
> When this parameter is used during a full restore of a database the indexes would not be applied.
> --only-indexes
> When this parameter is selected during a full restore of a database only the indexes would be applied.
This seems fairly redundant with the existing notion of "dump sections".
Have you experimented with "--section=post-data"?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, lance@illinois.edu
Subject: Re: pg_restore new parameter request
In-Reply-To: <1825.1448290213@sss.pgh.pa.us>
* 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