pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Palle Girgensohn <girgen@partitur.se>
Cc: Patrik Kudo <kudo@partitur.se>
Cc: pgsql-sql@postgreSQL.org <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] Duplicate tuples with unique index
Date: Wed, 26 Jan 2000 00:43:22 -0500 (EST)
Message-ID: <200001260543.AAA22584@candle.pha.pa.us> (raw)
In-Reply-To: <16091.948865123@sss.pgh.pa.us>

> 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



view thread (13+ messages)  latest in thread

Message-ID: <200001260543.AAA22584@candle.pha.pa.us>
Permalink:  ../200001260543.AAA22584@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200001260543.AAA22584@candle.pha.pa.us

 · 

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-sql@postgresql.org
  Cc: pgman@candle.pha.pa.us, tgl@sss.pgh.pa.us, girgen@partitur.se, kudo@partitur.se
  Subject: Re: [SQL] Duplicate tuples with unique index
  In-Reply-To: <200001260543.AAA22584@candle.pha.pa.us>
  References: <16091.948865123@sss.pgh.pa.us> <200001260543.AAA22584@candle.pha.pa.us>

* 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