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

Re: bug in join?

From: Laurette Cisneros <laurette(at)nextbus(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: bug in join?
Date: 2002-01-02 22:25:35
Message-ID: Pine.LNX.4.33.0201021414390.17257-100000@visor.corp.nextbus.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Yeah, the culprit appears to be vacuum analyze (vacuum alone doesn't do it).

The problem is that I fixed the original database by dropping and
recreating the tables populating them with backed up data.  And, now it
won't recreate (the values in pg_stats for them is lost).

Ugh.

I will keep trying to recreate it for you.

L.
On Wed, 2 Jan 2002, Tom Lane wrote:

> Laurette Cisneros <laurette(at)nextbus(dot)com> writes:
> > This join worked last week and today it gets and error:
> > select * from b, d
> >  where b.address = d.address;
> > It now fails with the following error:
> > ERROR:  join_selectivity: bad value -0.121693
>
> Probably what has changed is the pg_statistic data (VACUUM ANALYZE
> results).  Please send the results of
>
> select * from pg_stats where tablename = 'b';
> select * from pg_stats where tablename = 'd';
>
> 			regards, tom lane
>

-- 
Laurette Cisneros
(510) 420-3137
NextBus Information Systems, Inc.
www.nextbus.com
Passenger Information Everywhere


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-01-02 22:29:56
Subject: Re: bug in join?
Previous:From: Tom LaneDate: 2002-01-02 22:18:27
Subject: Re: Bulkloading using COPY - ignore duplicates?

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