From: Dimitri Fontaine <dfontaine@hi-media.com>
To: pgsql-performance@postgresql.org
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Merlin Moncure <mmoncure@gmail.com>
Cc: Ted Allen <tallen@blackducksoftware.com>
Subject: Re: Troubles dumping a very large table.
Date: Mon, 29 Dec 2008 13:48:37 +0100
Message-ID: <200812291348.39979.dfontaine@hi-media.com> (raw)
In-Reply-To: <14875.1230322730@sss.pgh.pa.us>
References: <495271EB.80508@blackducksoftware.com>
<b42b73150812261150k6b17b819i704b6b7720243eb8@mail.gmail.com>
<14875.1230322730@sss.pgh.pa.us>
Hi,
Le vendredi 26 décembre 2008, Tom Lane a écrit :
> Yeah, if he's willing to use COPY BINARY directly. AFAIR there is not
> an option to get pg_dump to use it.
Would it be possible to consider such an additional switch to pg_dump?
Of course the DBA has to know when to use it safely, but if the plan is to be
able to restore later dump on the same machine to recover from some human
error (oops, forgot the WHERE clause to this DELETE statement), it seems it
would be a good idea.
Regards,
--
dim
Attachments:
signature.asc (application/pgp-signature, 196B) download
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: dfontaine@hi-media.com, tgl@sss.pgh.pa.us, mmoncure@gmail.com, tallen@blackducksoftware.com
Subject: Re: Troubles dumping a very large table.
In-Reply-To: <200812291348.39979.dfontaine@hi-media.com>
* 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