From: | Jan Wieck <janwieck(at)yahoo(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Duplicate-key-detection failure case found in btree |
Date: | 2002-01-02 13:40:21 |
Message-ID: | 200201021340.g02DeMU06413@saturn.jw.home |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > The fix is to acquire the next page's write lock before we drop the
> > current page's. This is deadlock-free since no writer ever tries
> > to chain write-locks to the left (in fact the same thing is done in
> > the page split logic).
> >
> > I am not convinced that this explains any of the field reports of
> > duplicate rows that we've seen, but it's clearly a bug. Will commit
> > the fix shortly.
>
> Sounds good to me. Good find.
It always scares me that bugs like this can live untriggered
for multiple releases. What else is lingering under the
surface ...
And I absolutely agree with Tom, there is no connection
between this bug and the duplicate rows reported. Good catch
anyway.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
From | Date | Subject | |
---|---|---|---|
Next Message | Holger Krug | 2002-01-02 14:34:11 | Re: how to watch parse/plan trees |
Previous Message | Hannu Krosing | 2002-01-02 13:25:10 | how to watch parse/plan trees |