From: | Hannu Krosing <hannu(at)tm(dot)ee> |
---|---|
To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
Cc: | Tim Perdue <tperdue(at)valinux(dot)com>, Benjamin Adida <ben(at)mit(dot)edu>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: Article on MySQL vs. Postgres |
Date: | 2000-07-05 08:39:39 |
Message-ID: | 3962F44B.AEB0BABC@tm.ee |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The Hermit Hacker wrote:
>
> On Tue, 4 Jul 2000, Tim Perdue wrote:
>
> > Further, I have had situations where postgres actually had DUPLICATE
> > ids in a primary key field, probably due to some abort or other nasty
> > situation in the middle of a commit. How did I recover from That?
> > Well, I had to run a count(*) next to each ID and select out the rows
> > where there was more than one of each "unique" id, then reinsert those
> > rows and drop and rebuild the indexes and reset the sequences.
>
> Odd, were you using transactions here, or transactionless?
Actully I think I remember a recent bug report about some condition that
failed the uniqueness check when inside a transaction ;(
I think the report came with a fix ;)
------------
Hannu
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-07-05 08:46:52 | Re: Article on MySQL vs. Postgres |
Previous Message | Hannu Krosing | 2000-07-05 08:05:18 | Re: Proposed new libpq API |