Re: bug in join?
От | Laurette Cisneros |
---|---|
Тема | Re: bug in join? |
Дата | |
Msg-id | Pine.LNX.4.33.0201021414390.17257-100000@visor.corp.nextbus.com обсуждение исходный текст |
Ответ на | Re: bug in join? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: bug in join?
|
Список | 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@nextbus.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
В списке pgsql-hackers по дате отправления: