Re: pg_restore TODO - delay PK creation
От | Iain |
---|---|
Тема | Re: pg_restore TODO - delay PK creation |
Дата | |
Msg-id | 005901c4bfdc$f90d1130$7201a8c0@mst1x5r347kymb обсуждение исходный текст |
Ответ на | Re: pg_restore TODO - delay PK creation (Bruce Momjian <pgman@candle.pha.pa.us>) |
Список | 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@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 2:56 PM Subject: Re: [ADMIN] pg_restore TODO - delay PK creation > "Iain" <iain@mst.co.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
В списке pgsql-admin по дате отправления: