pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Iain <iain@mst.co.jp>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore TODO - delay PK creation
Date: Mon, 1 Nov 2004 14:42:16 +0900
Message-ID: <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb> (raw)
References: <200411010236.iA12a6V19009@candle.pha.pa.us>
	<017e01c4bfc0$6d17d140$7201a8c0@mst1x5r347kymb>
	<4249.1099280182@sss.pgh.pa.us>


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" <tgl@sss.pgh.pa.us>
To: "Iain" <iain@mst.co.jp>
Cc: "Bruce Momjian" <pgman@candle.pha.pa.us>; <pgsql-admin@postgresql.org>
Sent: Monday, November 01, 2004 12:36 PM
Subject: Re: [ADMIN] pg_restore TODO - delay PK creation


> "Iain" <iain@mst.co.jp> 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 




view thread (8+ messages)  latest in thread

Message-ID: <002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb>
Permalink:  ../002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb/
Also on:    postgresql.org/message-id/002101c4bfd5$8e87f2f0$7201a8c0@mst1x5r347kymb

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: iain@mst.co.jp, tgl@sss.pgh.pa.us, pgman@candle.pha.pa.us
  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>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox