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

Re: cluster test

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Joachim Wieland <joe(at)mcknight(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: cluster test
Date: 2007-05-25 15:39:24
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Joachim Wieland wrote:
> On Fri, May 25, 2007 at 10:33:41AM -0400, Tom Lane wrote:
> > We should find out why that's happening rather than just throwing an
> > ORDER BY at it.  Considering the number of buildfarm machines that
> > aren't showing any such problem, there must be something odd about
> > yours.  What's the platform?  What plan is being chosen for that SELECT?
> It's regular Debian Linux 2.6 on ix86.
> EXPLAIN SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass;
>                                             QUERY PLAN
> ---------------------------------------------------------------------------------------------------
>  Index Scan using pg_constraint_conrelid_index on pg_constraint (cost=0.00..8.27 rows=1 width=64)
>    Index Cond: (conrelid = 170982::oid)
> (2 rows)
> SELECT conname FROM pg_constraint WHERE conrelid = 'clstr_tst'::regclass;
>     conname
> ----------------
>  clstr_tst_con
>  clstr_tst_pkey
> (2 rows)
> As said before, it only happens with "make installcheck", not "make check".

Maybe there's an autovacuum run just before the test that causes
pg_constraint entries to be reordered?

Alvaro Herrera       
Oh, oh, las chicas galacianas, lo harán por las perlas,
¡Y las de Arrakis por el agua! Pero si buscas damas
Que se consuman como llamas, ¡Prueba una hija de Caladan! (Gurney Halleck)

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2007-05-25 16:00:21
Subject: Re: cluster test
Previous:From: Joachim WielandDate: 2007-05-25 15:28:13
Subject: Re: cluster test

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