SEO

#1 (**permalink**) 04-10-2008, 08:37 AM

The following bug has been logged online:

Bug reference: 1527
Logged by: Theo Petersen
Email address: tpetersen@ocv.com
PostgreSQL version: 7.4
Operating system: Linux (Gentoo)
Description: select retrieves 0 rows after vacuum analyze
Details:

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.

Regards,
...Theo

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

#2 (**permalink**) 04-10-2008, 08:38 AM

"Theo Petersen" <tpetersen@ocv.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.

Perhaps you should offer some details that would allow someone else to
replicate the problem.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

#3 (**permalink**) 04-10-2008, 08:38 AM

"Theo Petersen" <tpetersen@ocv.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...4/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/

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

BUG #1527: select retrieves 0 rows after vacuum analyze