Received: from candle.pha.pa.us (pgman@s5-03.ppp.op.net [209.152.195.67] (may be forged)) by hub.org (8.9.3/8.9.3) with ESMTP id AAA09140 for ; Wed, 26 Jan 2000 00:45:31 -0500 (EST) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id AAA22584; Wed, 26 Jan 2000 00:43:22 -0500 (EST) From: Bruce Momjian Message-Id: <200001260543.AAA22584@candle.pha.pa.us> Subject: Re: [SQL] Duplicate tuples with unique index In-Reply-To: <16091.948865123@sss.pgh.pa.us> from Tom Lane at "Jan 26, 2000 00:38:43 am" To: Tom Lane Date: Wed, 26 Jan 2000 00:43:22 -0500 (EST) CC: Palle Girgensohn , Patrik Kudo , "pgsql-sql@postgreSQL.org" X-Mailer: ELM [version 2.4ME+ PL66 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Bruce thinks that the pg_upgrade script will ensure that the system- > table tuples are all in frozen states (by VACUUMing them). I don't > trust it worth a dime, myself. Maybe it will work, but it hasn't been > proven in the field. So, if you'd like to try it, by all means do so > --- but make a pg_dump backup first! And let us know whether you have > problems or not! I see what you are saying. If a table created as part of the new pg_dump schema create matches a transaction that aborted in the old database, the table would be invalid. However, as you mentioned, once the tuple is marked as committed/rolled back, it doesn't consult. Basically, I was surprised pg_upgrade worked at all in any of the releases. It seems too good to be true. However, I have received very few problem reports about its use, and it does get used. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026