From: | "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | "Rafael Martinez, Guerrero" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> |
Subject: | Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
Date: | 2006-05-23 18:51:44 |
Message-ID: | b42b73150605231151r5c3e1a07r329eba455691dde0@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
On 5/19/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-05-23 19:18:21 | Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1) |
Previous Message | jois.de.vivre | 2006-05-23 18:36:18 | Re: meaning of PQresultStatus types |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-05-23 19:04:06 | Re: Update on sort-compression stuff |
Previous Message | Tom Lane | 2006-05-23 18:27:11 | Re: Update on sort-compression stuff |