X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A7BE43A3D5C for ; Mon, 1 Nov 2004 06:35:06 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 15329-08 for ; Mon, 1 Nov 2004 06:34:57 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 5E8823A3C7D for ; Mon, 1 Nov 2004 06:34:56 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iA16YnZ12602; Mon, 1 Nov 2004 15:34:49 +0900 Message-ID: <005901c4bfdc$f90d1130$7201a8c0@mst1x5r347kymb> From: "Iain" To: "Tom Lane" Cc: "Bruce Momjian" , References: <200411010236.iA12a6V19009@candle.pha.pa.us> <017e01c4bfc0$6d17d140$7201a8c0@mst1x5r347kymb> <4249.1099280182@sss.pgh.pa.us> <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb> <5219.1099288584@sss.pgh.pa.us> Subject: Re: pg_restore TODO - delay PK creation Date: Mon, 1 Nov 2004 15:35:21 +0900 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-2022-jp"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/10 X-Sequence-Number: 15395 Hi Bruce and Tom, I've got the picture now, thanks. I'll be sure to test it all pretty thoroughly before the day anyway. Thanks again. Iain ----- Original Message ----- From: "Tom Lane" To: "Iain" Cc: "Bruce Momjian" ; Sent: Monday, November 01, 2004 2:56 PM Subject: Re: [ADMIN] pg_restore TODO - delay PK creation > "Iain" writes: >> IIRC there has been a bug fix to the COPY command, regarding handling >> backslashed Ns or something like that sometime between 7.1 and 7.4, if I >> dump the 7.1 db with the 7.4 version of pg_dump then do I get the fixes >> to >> COPY? > > My recollection is that some of those changes were on the backend side, > and so they would affect the COPY data that pg_dump transcribes to the > dump file. Using the newer pg_dump will not make you any worse off > AFAIR, but it's not a magic fix for server-side bugs either ... > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 8: explain analyze is your friend