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

Re: pg_autovacuum w/ dbt2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mark Wong <markw(at)osdl(dot)org>
Cc: pgsql-hackers(at)postgresql(dot)org, testperf-general(at)pgfoundry(dot)org
Subject: Re: pg_autovacuum w/ dbt2
Date: 2004-12-21 22:56:47
Message-ID: 26568.1103669807@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-www
Mark Wong <markw(at)osdl(dot)org> writes:
> On Tue, Dec 21, 2004 at 02:23:41PM -0500, Tom Lane wrote:
>> Mark Wong <markw(at)osdl(dot)org> writes:
>>> [2004-12-20 15:48:18 PST]          The error is [ERROR:  failed to re-find parent key in "pk_district"
>> 
>> Yikes.  Is this reproducible?

> Yes, and I think there is one for each of the rollbacks that are
> occuring in the workload.  Except for the 1% that's supposed to happen
> for the new-order transaction.

Well, we need to find out what's causing that.  There are two possible
sources of that error (one elog in src/backend/access/nbtree/nbtinsert.c,
and one in src/backend/access/nbtree/nbtpage.c) and neither of them
should ever fire.

If you want to track it yourself, please change those elog(ERROR)s to
elog(PANIC) so that they'll generate core dumps, then build with
--enable-debug if you didn't already (--enable-cassert would be good too)
and get a debugger stack trace from the core dump.

Otherwise, can you extract a test case that causes this without needing
vast resources to run?

			regards, tom lane

In response to

Responses

pgsql-www by date

Next:From: Mark WongDate: 2004-12-21 23:15:54
Subject: Re: pg_autovacuum w/ dbt2
Previous:From: Mark WongDate: 2004-12-21 22:47:19
Subject: Re: pg_autovacuum w/ dbt2

pgsql-hackers by date

Next:From: Mark WongDate: 2004-12-21 23:15:54
Subject: Re: pg_autovacuum w/ dbt2
Previous:From: Mark WongDate: 2004-12-21 22:47:19
Subject: Re: pg_autovacuum w/ dbt2

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