| From: | svn(at)pgadmin(dot)org |
|---|---|
| To: | pgadmin-hackers(at)postgresql(dot)org |
| Subject: | SVN Commit by dpage: r7807 - trunk/pgadmin3/pgadmin/schema |
| Date: | 2009-04-15 09:06:29 |
| Message-ID: | 200904150906.n3F96T1k030839@developer.pgadmin.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
Author: dpage
Date: 2009-04-15 10:06:29 +0100 (Wed, 15 Apr 2009)
New Revision: 7807
Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=7807&view=rev
Log:
Greenplum stores the number of rows per segmentDatabase (actually the max of any of the segDBs) in pg_class.reltuples, not the total number of tuples.
This causes the stats to display wrong values, and causes pgAdmin to warn that Analyze is needed when it is not.
This simple patch multiplies the reltuples x gp_segments, so that we get a better value.
Of course, it only does this for Greenplum connections.
[Chuck McDevitt]
Modified:
trunk/pgadmin3/pgadmin/schema/gpPartition.cpp
trunk/pgadmin3/pgadmin/schema/pgTable.cpp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-04-15 09:06:44 | Re: Greenplum patch for estimated rowcounts being wrong. |
| Previous Message | Chuck McDevitt | 2009-04-15 02:24:19 | Greenplum patch for estimated rowcounts being wrong. |