Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 29 Dec 2008 13:48:37 +0100
- Message-id: <200812291348.39979.dfontaine@hi-media.com> <text/plain>
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
Attachment:
signature.asc
Description: This is a digitally signed message part.
- References:
- Troubles dumping a very large table.
- From: Ted Allen
- Re: Troubles dumping a very large table.
- From: Merlin Moncure
- Re: Troubles dumping a very large table.
- From: Tom Lane
- Troubles dumping a very large table.
- Prev by Date: Re: Slow table update
- Next by Date: Re: Slow table update - SOLVED!
- Previous by thread: Re: Troubles dumping a very large table.
- Next by thread: Re: Troubles dumping a very large table.
- Indexes: