It's not an overflow, instead the column is scanned as int, resulting in reltuples=7 (which isn't too precise :-)
-----Original Message-----
From: Constantin Stefanov [mailto:[EMAIL PROTECTED] Sent: 23 October 2003 08:59
To: [EMAIL PROTECTED]
Subject: Re: [pgadmin-support] Very slow viewing of large table.
SELECT relname, reltuples FROM pg_class;For my table there is
------------------------------
accounting# SELECT relname, reltuples FROM pg_class where relname='ip_accounting';
relname | reltuples
---------------+-------------
ip_accounting | 7.71493e+07
------------------------------
May be there is some overflow or incorrect result parsing?
Hmm, shouldn't be - the code appears to use longs everywhere. I can't
really spend time on this now though - Andreas, can you take a look
please?
I changed the types of rows to wxLongLong, and estimatedRows to double now.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org