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

Re: Duplicate values found when reindexing unique index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Mason Hale <masonhale(at)gmail(dot)com>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Duplicate values found when reindexing unique index
Date: 2007-12-31 17:33:09
Message-ID: 7114.1199122389@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Mon, 2007-12-31 at 11:53 -0500, Tom Lane wrote:
>> The state of the ...0058 file might be explained by the theory that
>> you'd archived it a bit too late (after the first page had been
>> overwritten with newer WAL data), 

> The interlock with .ready and .done should prevent reuse of a file. So
> the only way this could happen is if the archive_command queued a
> request to copy, rather than performing the copy immediately.
> So I was going to say "thats not possible", but perhaps rsync might
> become confused by the file renaming mechanism we use? 

Actually, the other problem with that theory is that the slave swallowed
the file without complaint.  Since the WAL reader code does check that
the page header contains the expected address, this seems to imply that
what the slave saw must have had 422/58 in it, not the 423/C1 we see
now.  So what needs to be explained is why what Mason is looking at now
is different from what the slave saw ten days ago.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Simon RiggsDate: 2007-12-31 17:47:59
Subject: Re: Duplicate values found when reindexing unique index
Previous:From: Tom LaneDate: 2007-12-31 17:23:54
Subject: Re: Duplicate values found when reindexing unique index

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