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 8C8DDD1E943 for ; Thu, 25 Mar 2004 16:31:20 +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 73278-01 for ; Thu, 25 Mar 2004 12:31:18 -0400 (AST) Received: from ecintweb.eldocomp.com (ecintweb.eldocomp.com [205.159.99.8]) by svr1.postgresql.org (Postfix) with ESMTP id C264BD1ECB5 for ; Thu, 25 Mar 2004 12:31:12 -0400 (AST) Received: by ecintweb.eldocomp.com with XWall v3.29 ; Thu, 25 Mar 2004 09:31:16 -0700 From: Naomi Walker To: Tom Lane Cc: Bruce Momjian , Tsirkin Evgeny , Naomi Walker , "Mark M. Huber" , "pgsql-admin@postgresql.org" Subject: Re: backup and recovery Date: Thu, 25 Mar 2004 09:29:26 -0700 X-Assembled-By: XWall v3.29 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Message-ID: <5.1.0.14.2.20040325084622.022a5198@imap.eldocomp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/325 X-Sequence-Number: 12894 > >Of course, practice often differs from theory, but I wonder whether we >aren't talking about palliating a symptom instead of fixing the real >problem. Certainly a good point, since I might be using the tools to do things that= =20 were unintended. We have development, test, and production areas for our= =20 applications using postgres. I regularly move rows and tables from one=20 place to another, and often one platform to another. For example, i'll dump a table with a group of customers from one machine,= =20 and add all those rows to the test and development areas, and sometimes=20 issues occur. It is not the case that I always move whole databases of=20 instances from place to place. We've also written several tools that "COPY table from stdin", followed by= =20 specific "selects" to move rows around. Instead of suggesting the solution, I should probably state the problem. 1) Before performing any maintenance on a table, we unload it first, just= =20 in case. We need quick reload methods. psql typically works well, but is= =20 sometimes slow. 2) We could really use a generic tool to unload "selected" rows from a=20 table, and move the unload somewhere else to reload. [NOTE: we had to=20 stick in all sorts of perl things to deal with \n-like stuff).] Perhaps i'm using the wrong tools, but I am trainable. We are running postgres 7.3.4 on Solaris and Redhat Linux servers. Naomi ---------------------------------------------------------------------------= ---------------------------------------------- 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= =20 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 w= hom it is addressed, and may contain information that is privileged, confid= ential and exempt from disclosure under applicable law. If you are not the = intended addressee, nor authorized to receive for the intended addressee, y= ou are hereby notified that you may not use, copy, disclose or distribute t= o anyone the message or any information contained in the message. If you ha= ve received this message in error, please immediately advise the sender by = reply email, and delete the message. Thank you.