From: | "Iain" <iain(at)mst(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_restore TODO - delay PK creation |
Date: | 2004-11-01 06:35:21 |
Message-ID: | 005901c4bfdc$f90d1130$7201a8c0@mst1x5r347kymb |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Iain" <iain(at)mst(dot)co(dot)jp>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>; <pgsql-admin(at)postgresql(dot)org>
Sent: Monday, November 01, 2004 2:56 PM
Subject: Re: [ADMIN] pg_restore TODO - delay PK creation
> "Iain" <iain(at)mst(dot)co(dot)jp> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Jain, Neeraj | 2004-11-01 07:35:26 | creating database fails on windows XP: Postgres 8.0 |
Previous Message | Tom Lane | 2004-11-01 05:56:24 | Re: pg_restore TODO - delay PK creation |