Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id A96B364FD20 for ; Mon, 29 Dec 2008 08:48:55 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 45089-10 for ; Mon, 29 Dec 2008 08:48:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from smtp1.hi-media-techno.com (smtp1.hi-media-techno.com [195.158.241.85]) by mail.postgresql.org (Postfix) with ESMTP id B785564FD19 for ; Mon, 29 Dec 2008 08:48:52 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by smtp1.hi-media-techno.com (Postfix) with ESMTP id D667A93D4E; Mon, 29 Dec 2008 13:48:49 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at smtp1.backbone.hi-media-techno.com Received: from smtp1.hi-media-techno.com ([127.0.0.1]) by localhost (smtp1.backbone.hi-media-techno.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tUjdfahmoXXZ; Mon, 29 Dec 2008 13:48:48 +0100 (CET) Received: from mail1.hi-media-techno.com (unknown [192.168.27.12]) by smtp1.hi-media-techno.com (Postfix) with ESMTP id 1688D93BD4; Mon, 29 Dec 2008 13:48:48 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail1.hi-media-techno.com (Postfix) with ESMTP id 0DC5E6D842E; Mon, 29 Dec 2008 13:48:48 +0100 (CET) X-Virus-Scanned: amavisd-new at Received: from mail1.hi-media-techno.com ([127.0.0.1]) by localhost (mail1.hi-media-techno.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Uz9Att7-No0W; Mon, 29 Dec 2008 13:48:47 +0100 (CET) Received: from dim.local (unknown [83.167.62.196]) by mail1.hi-media-techno.com (Postfix) with ESMTP id BFAEA6D8791; Mon, 29 Dec 2008 13:48:47 +0100 (CET) From: Dimitri Fontaine Organization: Hi-Media To: pgsql-performance@postgresql.org Subject: Re: Troubles dumping a very large table. Date: Mon, 29 Dec 2008 13:48:37 +0100 User-Agent: KMail/1.9.9 Cc: Tom Lane , "Merlin Moncure" , "Ted Allen" References: <495271EB.80508@blackducksoftware.com> <14875.1230322730@sss.pgh.pa.us> In-Reply-To: <14875.1230322730@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart15580696.UY1FirqEBA"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200812291348.39979.dfontaine@hi-media.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/222 X-Sequence-Number: 32258 --nextPart15580696.UY1FirqEBA Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi, Le vendredi 26 d=C3=A9cembre 2008, Tom Lane a =C3=A9crit=C2=A0: > Yeah, if he's willing to use COPY BINARY directly. AFAIR there is not > an option to get pg_dump to use it. =20 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=20 able to restore later dump on the same machine to recover from some human=20 error (oops, forgot the WHERE clause to this DELETE statement), it seems it= =20 would be a good idea. Regards, =2D-=20 dim --nextPart15580696.UY1FirqEBA Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAklYxyUACgkQlBXRlnbh1bnwVACgpFQN+iT3iGc2R3iM5FFJnaLB vycAnAqHFL9W+2giySGxJuvcV1DhMgAZ =REYu -----END PGP SIGNATURE----- --nextPart15580696.UY1FirqEBA--