X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 4FF8FD1D5A3 for ; Wed, 24 Mar 2004 17:54:21 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 27303-09 for ; Wed, 24 Mar 2004 13:54:14 -0400 (AST) Received: from smtp2.actcom.co.il (mail.actcom.net.il [192.114.47.15]) by svr1.postgresql.org (Postfix) with ESMTP id B619CD1CA50 for ; Wed, 24 Mar 2004 13:54:12 -0400 (AST) Received: from machenai-2h2ozp (l192-117-121-19.broadband.actcom.net.il [192.117.121.19]) by smtp2.actcom.co.il (8.12.8/8.12.8) with ESMTP id i2OHruRi004748; Wed, 24 Mar 2004 19:54:00 +0200 Cc: "pgsql-admin@postgresql.org" To: Naomi Walker , "Mark M. Huber" Subject: Re: [Retrieved]RE: backup and recovery References: <5.1.0.14.2.20040323170131.05e1e290@imap.eldocomp.com> Message-ID: From: Tsirkin Evgeny Content-Type: text/plain; format=flowed; charset=utf-8 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Date: Wed, 24 Mar 2004 19:49:12 +0200 In-Reply-To: <5.1.0.14.2.20040323170131.05e1e290@imap.eldocomp.com> User-Agent: Opera7.20/Win32 M2 build 3144 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/314 X-Sequence-Number: 12883 Isn't it better to put this say in the pg_restore or integrate such thing into psql ? On Tue, 23 Mar 2004 17:02:36 -0700, Naomi Walker wrote: > > I'm not sure of the correct protocol for getting things on the "todo" > list. Whom shall we beg? > > > At 10:13 AM 3/22/2004, Mark M. Huber wrote: >> That sounds like a brilliant idea, who do we say it to make it so? >> >> Mark H >> >> -----Original Message----- >> From: Naomi Walker [mailto:nwalker@eldocomp.com] >> Sent: Monday, March 22, 2004 8:19 AM >> To: Mark M. Huber >> Cc: Naomi Walker; pgsql-admin@postgresql.org >> Subject: Re: [ADMIN] backup and recovery >> >> >> That brings up a good point. It would be extremely helpful to add two >> parameters to pg_dump. One, to add how many rows to insert before a >> commit, and two, to live through X number of errors before dying (and >> putting the "bad" rows in a file). >> >> >> At 10:15 AM 3/19/2004, Mark M. Huber wrote: >> >What it was that I guess the pg_dump makes one large transaction and >> our >> >shell script wizard wrote a perl program to add a commit transaction >> >every 500 rows or what every you set. Also I should have said that we >> were >> >doing the recovery with the insert statements created from pg_dump. >> So... >> >my 500000 row table recovery took < 10 Min. >> > >> >Thanks for your help. >> > >> >Mark H >> > >> > >> >- >> >> ------------------------------------------------------------------------------------------------------------------------- >> Naomi Walker Chief Information Officer >> Eldorado Computing, Inc. >> nwalker@eldocomp.com 602-604-3100 >> ------------------------------------------------------------------------------------------------------------------------- >> Forget past mistakes. Forget failures. Forget everything except what >> you're >> going to do now and do it. >> - William Durant, founder of General Motors >> ------------------------------------------------------------------------------------------------------------------------ > > Naomi Walker Chief Information Officer > Eldorado Computing, Inc. > nwalker@eldocomp.com 602-604-3100 > ------------------------------------------------------------------------------------------------------------------------- > Forget past mistakes. Forget failures. Forget everything except what > you're > going to do now and do it. > - William Durant, founder of General Motors > ------------------------------------------------------------------------------------------------------------------------ > > -- CONFIDENTIALITY NOTICE -- > > This message is intended for the sole use of the individual and entity > to whom it is addressed, and may contain information that is privileged, > confidential and exempt from disclosure under applicable law. If you are > not the intended addressee, nor authorized to receive for the intended > addressee, you are hereby notified that you may not use, copy, disclose > or distribute to anyone the message or any information contained in the > message. If you have received this message in error, please immediately > advise the sender by reply email, and delete the message. Thank you. > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly