[postgis-users] Vacuum analyse ERROR: Operation on twoGEOMETRIESwith different SRIDs
Mark Cave-Ayland
m.cave-ayland at webbased.co.uk
Wed Jun 15 03:33:12 PDT 2005
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On
> Behalf Of strk at refractions.net
> Sent: 15 June 2005 10:56
> To: 'PostGIS Users Discussion'
> Subject: Re: [postgis-users] Vacuum analyse ERROR: Operation
> on twoGEOMETRIESwith different SRIDs
>
>
> On Wed, Jun 15, 2005 at 10:42:31AM +0100, Mark Cave-Ayland wrote: ...
> > I'm just wondering if it's to do with ANALYZE invoking a geometry
> > comparison using the btree operators for "less than" and
> "equals" for
> > PostgreSQL < 8.0.
>
> mmm.. I think you're right, should we make btree ops SRID
> immune or consider this behaviour correct (analisys found a
> SRID mix error in a table).
>
> --strk;
Hi strk,
Having mixed SRID geometries in a column is, of course, completely
non-sensical since the results of any spatial query could be invalid. I
would vote that the behaviour is correct, since it would then encourage the
user to sort out the column data first. However, I do think the behaviour is
poor to simply error out on ANALYZE, but of course there is nothing we can
hook into before 8.0 :(
The only think I think we could possibly do is reduce the SRID mismatch
check from elog(ERROR) to elog(WARNING), but I'm not sure I'd be too keen to
do that...
Kind regards,
Mark.
------------------------
WebBased Ltd
17 Research Way
Tamar Science Park
Plymouth
PL6 8BT
T: +44 (0)1752 797131
F: +44 (0)1752 791023
W: http://www.webbased.co.uk
More information about the postgis-users
mailing list