Re: BUG #1527: select retrieves 0 rows after vacuum analyze

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Theo Petersen <tpetersen(at)ocv(dot)com>, pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #1527: select retrieves 0 rows after vacuum analyze
Date: 2005-03-05 06:20:27
Message-ID: 20050305062027.GA68366@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Theo Petersen" <tpetersen(at)ocv(dot)com> writes:
> I have a database (network monitoring data created by OpenNMS) that exhibits
> this behavior:
>
> 1) I restore the database from a production backup.
> 2) I perform a select that joins four tables, and get 9 rows of output.
> 3) I use the command VACUUM ANALYZE to maintain the database files.
> 4) I perform the same select and get 0 rows of output.
>
> I've reduced it to those steps to verify the problem.

Are you perchance doing joins involving INET or CIDR types where
the old database is 7.3.x and the new database is 7.4.x? I ask
because I discovered a problem with the 7.4.x = operator when I was
(hastily) writing the prototype for the application I think you're
working on.

http://archives.postgresql.org/pgsql-general/2004-04/msg00453.php

If this is the problem you're having, then it should be mentioned
on the project Wiki that Chris F. set up, if it still exists.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Hashem Masoud 2005-03-06 20:25:47 Likely typo in FAQ_DEV.html
Previous Message Kris Jurka 2005-03-05 05:11:06 Re: BUG #1525: wrong time when getting timestamp from date