[postgis-devel] estimated_extent & pg_statistic
m.cave-ayland at webbased.co.uk
Fri Mar 10 05:18:50 PST 2006
> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net [mailto:postgis-devel-
> bounces at postgis.refractions.net] On Behalf Of strk at refractions.net
> Sent: 08 March 2006 18:17
> To: 'PostGIS Development Discussion'
> Subject: Re: [postgis-devel] estimated_extent & pg_statistic
> > Is there any particular reason why views cause a problem?
> Ehm... dump/reload ?
> Our "soft-upgrade" procedure is not currently able to add a view.
I'm not a Perl hacker myself, but looking at the script I don't think it
would be too hard to do if we decided to take that route. Currently there
are no changes to the pre-8.0 code since it relies on having SELECT
permissions on the geometry_columns table to read the column statistics, and
all users will need that anyway if they are using
> estimated_extent is only available when building against pgsql >= 73
> so no problem there.
Are you sure? At this end, the only #ifdef I can see for USE_VERSION >= 73
is in lines 1399-1415 of lwpostgis.sql.in, and estimated_extent() is
definitely outside of it...
> I've no time to check the patch for this week. If people can test
> it with different pgsql versions (from 73 to 81) that'll help.
Yup, if Martin in particular could test it in his setup, that would be very
17 Research Way
T: +44 (0)1752 797131
F: +44 (0)1752 791023
This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify the sender. You should not copy it or
use it for any purpose nor disclose or distribute its contents to any other
More information about the postgis-devel