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

Re: Index corruption

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Marko Kreen <markokr(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marc Munro <marc(at)bloodnok(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index corruption
Date: 2006-06-30 15:33:41
Message-ID: 44A54455.1080700@Yahoo.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 6/30/2006 11:17 AM, Marko Kreen wrote:

> On 6/30/06, Jan Wieck <JanWieck(at)yahoo(dot)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(at)Yahoo(dot)com #

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-06-30 15:55:22
Subject: Re: Index corruption
Previous:From: Stefan KaltenbrunnerDate: 2006-06-30 15:32:06
Subject: Re: GIN index creation extremely slow ?

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