Skip site navigation (1) Skip section navigation (2)

Re: Duplicate-key-detection failure case found in btree

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Duplicate-key-detection failure case found in btree
Date: 2002-01-01 20:49:31
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> 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.

  Bruce Momjian                        |
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

In response to


pgsql-hackers by date

Next:From: Adam HaberlachDate: 2002-01-01 22:26:47
Subject: SET DATESTYLE to time_t style for client libraries?
Previous:From: Tom LaneDate: 2002-01-01 19:46:24
Subject: Duplicate-key-detection failure case found in btree

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group