Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Fri, 30 Jun 2006 11:33:41 -0400
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 #
- Follow-Ups:
- Re: Index corruption
- From: Tom Lane
- Re: Index corruption
- References:
- Index corruption
- From: Marc Munro
- Re: Index corruption
- From: Tom Lane
- Re: Index corruption
- From: Marc Munro
- Re: Index corruption
- From: Tom Lane
- Re: Index corruption
- From: Marko Kreen
- Re: Index corruption
- From: Tom Lane
- Re: Index corruption
- From: Jan Wieck
- Re: Index corruption
- From: Marko Kreen
- Index corruption
- Prev by Date: Re: GIN index creation extremely slow ?
- Next by Date: Re: Index corruption
- Previous by thread: Re: Index corruption
- Next by thread: Re: Index corruption
- Indexes: