Re: Index corruption - Mailing list pgsql-hackers

From Jan Wieck
Subject Re: Index corruption
Date
Msg-id 44A54455.1080700@Yahoo.com
Whole thread Raw
In response to Re: Index corruption  ("Marko Kreen" <markokr@gmail.com>)
Responses Re: Index corruption  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 6/30/2006 11:17 AM, Marko Kreen wrote:

> On 6/30/06, Jan Wieck <JanWieck@yahoo.com> wrote:
>> With the final implementation of log switching, the problem of xxid
>> wraparound will be avoided entirely. Every now and then slony will
>> switch from one to another log table and when the old one is drained and
>> logically empty, it is truncated, which should reinitialize all indexes.
> 
> If the xxid-s come from different DB-s, then there can still be problems.

How so? They are allways part of a multi-key index having the 
originating node ID first.


Jan

-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck@Yahoo.com #


pgsql-hackers by date:

Previous
From: Stefan Kaltenbrunner
Date:
Subject: Re: GIN index creation extremely slow ?
Next
From: Tom Lane
Date:
Subject: Re: Index corruption