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

Re: Going for "all green" buildfarm results

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Going for "all green" buildfarm results
Date: 2006-07-30 05:40:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> FWIW: lionfish had a weird make check error 3 weeks ago which I
>> (unsuccessfully) tried to reproduce multiple times after that:
> Weird.
>   SELECT ''::text AS eleven, unique1, unique2, stringu1 
>                 FROM onek WHERE unique1 < 50 
>                 ORDER BY unique1 DESC LIMIT 20 OFFSET 39;
> ! ERROR:  could not open relation with OID 27035
> AFAICS, the only way to get that error in HEAD is if ScanPgRelation
> can't find a pg_class row with the mentioned OID.  Presumably 27035
> belongs to "onek" or one of its indexes.  The very next command also
> refers to "onek", and doesn't fail, so what we seem to have here is
> a transient lookup failure.  We've found a btree bug like that once
> before ... wonder if there's still one left?

FYI: lionfish just managed to hit that problem again:


In response to


pgsql-hackers by date

Next:From: Alvaro HerreraDate: 2006-07-30 06:20:05
Subject: Re: Going for "all green" buildfarm results
Previous:From: Bruce MomjianDate: 2006-07-30 02:16:27
Subject: Re: PATCH to allow concurrent VACUUMs to not lock each

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