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

Re: Index corruption

From: "Marko Kreen" <markokr(at)gmail(dot)com>
To: "Jan Wieck" <JanWieck(at)yahoo(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:17:26
Message-ID: e51f66da0606300817o7a39137eh8e89fdc619b35216@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

-- 
marko

In response to

Responses

pgsql-hackers by date

Next:From: Stefan KaltenbrunnerDate: 2006-06-30 15:32:06
Subject: Re: GIN index creation extremely slow ?
Previous:From: Jan WieckDate: 2006-06-30 14:44:07
Subject: Re: Index corruption

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