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 A909A3A4413 for ; Mon, 1 Nov 2004 05:41:59 +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 03752-03 for ; Mon, 1 Nov 2004 05:41:57 +0000 (GMT) Received: from millenium.mst.co.jp (unknown [210.230.185.241]) by svr1.postgresql.org (Postfix) with ESMTP id 9BE053A4423 for ; Mon, 1 Nov 2004 05:41:56 +0000 (GMT) Received: from mst1x5r347kymb (lc12114 [192.168.1.114]) by millenium.mst.co.jp (8.11.6p2/3.7W) with SMTP id iA15fiZ12390; Mon, 1 Nov 2004 14:41:44 +0900 Message-ID: <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb> From: "Iain" To: "Tom Lane" , "Bruce Momjian" Cc: References: <200411010236.iA12a6V19009@candle.pha.pa.us> <017e01c4bfc0$6d17d140$7201a8c0@mst1x5r347kymb> <4249.1099280182@sss.pgh.pa.us> Subject: Re: pg_restore TODO - delay PK creation Date: Mon, 1 Nov 2004 14:42:16 +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/8 X-Sequence-Number: 15393 Thanks guys, I'll keep that in mind. Sorry to keep on about this, but please bear with me for one more m(_ _)m <-- this is me abasing myself before you 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? The documentation for psql is clear that it uses a frontend version of copy so I'm gonna assume for now (until I test it am told eitherway) that psql 7.4 will use the later version of copy against a 7.1 db. Because the old db is badly in need of maintenance and some tables take a considerable time to unload, I was considering running a few concurrent sessions of psql and using the COPY command so I can start loading smaller tables on the new server while the bigger ones are still unloading. Most of the old tables have to be transformed to a new format, and I wanna get home by the last train if possible :) . regards iain ----- Original Message ----- From: "Tom Lane" To: "Iain" Cc: "Bruce Momjian" ; Sent: Monday, November 01, 2004 12:36 PM Subject: Re: [ADMIN] pg_restore TODO - delay PK creation > "Iain" writes: >> Out of interest, what is the word on using newer versions of pg_dump on >> older verisons of the DB - is it is possible or even wise to unload a >> 7.1 >> DB with the 7.4 version of pg? > > Standard, recommended procedure is to use the later version of pg_dump > to unload data from the old server. This gets you the benefit of any > bug fixes in the newer pg_dump (of which there are always some...) > > Note that pg_dump is usually not designed to produce output that will > load into back-release servers, so this only applies to cross-version > upgrades. You can't use the 7.4 pg_dump against a 7.1 server and expect > to get a dump file that will load back into the 7.1 server --- more than > likely, the dump file will make use of features that weren't in 7.1. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 7: don't forget to increase your free space map settings