backpatch fix for bug #1808053. we go with numeric, which will lose precision, but can

handle values larger than int. Since reltuples is pretty fuzzy anyway, this seems like a fair balance.

1 files changed, 2 insertions, 2 deletions

diff --git a/classes/database/Postgres72.php b/classes/database/Postgres72.php
index a533f4e7..058cae72 100644
--- a/classes/database/Postgres72.php
+++ b/classes/database/Postgres72.php
@@ -4,7 +4,7 @@
  * A class that implements the DB interface for Postgres
  * Note: This class uses ADODB and returns RecordSets.
  *
- * $Id: Postgres72.php,v 1.87.2.1 2007/10/03 01:12:28 xzilla Exp $
+ * $Id: Postgres72.php,v 1.87.2.2 2007/10/18 12:35:07 xzilla Exp $
  */
 
 
@@ -205,7 +205,7 @@ class Postgres72 extends Postgres71 {
 		$sql = "SELECT NULL AS nspname, c.relname, 
 					(SELECT usename FROM pg_user u WHERE u.usesysid=c.relowner) AS relowner, 
 					(SELECT description FROM pg_description pd WHERE c.oid=pd.objoid AND objsubid = 0) AS relcomment,
-					reltuples::bigint
+					reltuples::numeric
 			 FROM pg_class c WHERE c.relkind='r' {$where}ORDER BY relname";
 		return $this->selectSet($sql);
 	}