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

Re: Index corruption

From: Hannu Krosing <hannu(at)skype(dot)net>
To: Chris Browne <cbbrowne(at)acm(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Index corruption
Date: 2006-06-29 21:23:45
Message-ID: 1151616225.2845.1.camel@localhost.localdomain (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Ühel kenal päeval, N, 2006-06-29 kell 16:42, kirjutas Chris Browne:
> marc(at)bloodnok(dot)com (Marc Munro) writes:
> > As you see, slony is attempting to enter one tuple
> > ('374520943','22007','0') two times.
> >
> > Each previous time we have had this problem, rebuilding the indexes on
> > slony log table (sl_log_1) has fixed the problem.  I have not reindexed
> > the table this time as I do not want to destroy any usable evidence.
> We have seen this phenomenon on 7.4.8 several times; pulled dumps of
> sl_log_1 and index files that Jan Wieck looked at, which alas hasn't
> led to a fix.
> He did, mind you, find some concurrency pattern that led, if memory
> serves, to 7.4.12's release.  We had experienced cases where there was
> some worse corruption that required that we rebuild replicas from
> scratch :-(.

How well did you check the C-language triggers and special slony
functions for possibly corrupting some backend/shared-mem structures ?

Hannu Krosing
Database Architect
Skype Technologies OÜ
Akadeemia tee 21 F, Tallinn, 12618, Estonia

Skype me:  callto:hkrosing
Get Skype for free:

In response to

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-06-29 21:37:41
Subject: Re: [HACKERS] Non-transactional pg_class, try 2
Previous:From: Tom LaneDate: 2006-06-29 21:23:04
Subject: Re: Index corruption

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