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 4AF133A442C for ; Mon, 1 Nov 2004 05:56:38 +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 07096-05 for ; Mon, 1 Nov 2004 05:56:29 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 6906E3A4455 for ; Mon, 1 Nov 2004 05:56:29 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iA15uOWw005220; Mon, 1 Nov 2004 00:56:24 -0500 (EST) To: "Iain" Cc: "Bruce Momjian" , pgsql-admin@postgresql.org Subject: Re: pg_restore TODO - delay PK creation In-reply-to: <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb> References: <200411010236.iA12a6V19009@candle.pha.pa.us> <017e01c4bfc0$6d17d140$7201a8c0@mst1x5r347kymb> <4249.1099280182@sss.pgh.pa.us> <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb> Comments: In-reply-to "Iain" message dated "Mon, 01 Nov 2004 14:42:16 +0900" Date: Mon, 01 Nov 2004 00:56:24 -0500 Message-ID: <5219.1099288584@sss.pgh.pa.us> From: Tom Lane 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/9 X-Sequence-Number: 15394 "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