Re: Troubles dumping a very large table.

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Ted Allen" <tallen(at)blackducksoftware(dot)com>
Subject: Re: Troubles dumping a very large table.
Date: 2008-12-29 12:48:37
Message-ID: 200812291348.39979.dfontaine@hi-media.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Laszlo Nagy 2008-12-29 13:11:48 Re: Slow table update - SOLVED!
Previous Message Gregory Williamson 2008-12-29 11:00:44 Re: Slow table update