Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1) - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1)
Date
Msg-id b42b73150605231151r5c3e1a07r329eba455691dde0@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1)
List pgsql-hackers
On 5/19/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This only affects the 7.4 and 8.0 branches, because earlier and later
> versions of Postgres don't use this technique for detecting duplicates.
> But it's surprising we didn't find it before.

hm. about a year ago I reported a case where the database allowed
multiple records with the same p-key which were causing problems with
dump/reload from 8.0->8.1.  It was pretty rare, but it looked like
under certain circumstances unique constraint was not getting applied.I was unable to reproduce it, though.

Is it possible that this bug was the cause of that particular problem?

Merlin


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Update on sort-compression stuff
Next
From: Simon Riggs
Date:
Subject: Re: Update on sort-compression stuff