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).
I will keep trying to recreate it for you.
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
NextBus Information Systems, Inc.
Passenger Information Everywhere
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2002-01-02 22:29:56|
|Subject: Re: bug in join? |
|Previous:||From: Tom Lane||Date: 2002-01-02 22:18:27|
|Subject: Re: Bulkloading using COPY - ignore duplicates? |