Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id CC2B49FA0EF for ; Wed, 20 Dec 2006 05:38:02 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 24485-10 for ; Wed, 20 Dec 2006 05:37:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 7A5129F939F for ; Wed, 20 Dec 2006 05:37:56 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.3 Received: from mx.imatech.net (unknown [81.255.215.253]) by svr4.postgresql.org (Postfix) with ESMTP id E3E8D5AF8C8 for ; Wed, 20 Dec 2006 09:37:54 +0000 (GMT) X-AuthUser: olivier.boissard@cerene.fr Received: from [200.200.200.34] ([195.6.193.141]:39443) by mx.imatech.net with [XMail 1.23 ESMTP Server] id for from ; Wed, 20 Dec 2006 10:37:17 +0100 Message-ID: <4589046D.60603@cerene.fr> Date: Wed, 20 Dec 2006 10:37:49 +0100 From: Olivier Boissard Organization: cerene services User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Chris Hoover Cc: arnaulist@andromeiberica.com, pgsql-admin@postgresql.org Subject: Re: Suggestions needed about how to dump/restore a database References: <45881D1A.6090904@andromeiberica.com> <1d219a6f0612191344x2f772a7el8ef9117a057c9cd8@mail.gmail.com> In-Reply-To: <1d219a6f0612191344x2f772a7el8ef9117a057c9cd8@mail.gmail.com> Content-Type: multipart/mixed; boundary="------------000900090804050709060109" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/279 X-Sequence-Number: 24071 This is a multi-part message in MIME format. --------------000900090804050709060109 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Chris Hoover a écrit : > One other option is to shut the database down competely, and then do a > copy of the file system the new server. I have done this when I need > to move a very large database to a new server. I can copy 500GB's in > a couple of hours, where restoring my large databases backups would > take 10+ hours. Just make sure you are keeping postgres at the same > version level. > > HTH, > > Chris > > On 12/19/06, *Arnau* > wrote: > > Hi all, > > I've got a DB in production that is bigger than 2GB that dumping it > takes more than 12 hours. I have a new server to replace this old one > where I have restore the DB's dump. The problem is I can't afford to > have the server out of business for so long, so I need your advice > about > how you'd do this dump/restore. The big amount of data is placed > in two > tables (statistics data), so I was thinking in dump/restore all > except > this two tables and once the server is running again I'd dump/restore > this data. The problem is I don't know how exactly do this. > > Any suggestion? > > Thanks > -- > Arnau > > > ---------------------------(end of > broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match > > How many tables have you got in your database ? If you have only a few tables you can dump them one at a time pgdump -t .... Olivier --------------000900090804050709060109 Content-Type: text/x-vcard; charset=utf-8; name="olivier.boissard.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="olivier.boissard.vcf" begin:vcard fn:Olivier Boissard n:Boissard;Olivier org:Cerene Services adr:;;3 rue Archimede;La Chapelle Saint Luc;;10000;France email;internet:olivier.boissard@cerene.fr tel;work:03.25.74.11.78 tel;fax:03.25.78.39.67 version:2.1 end:vcard --------------000900090804050709060109--