[postgis-devel] PostgreSQL 7.5 and PostGIS 0.8.1 or cvs

[Mark Cave-Ayland]

Hi Craig,

A few of us have been using the CVS version of PostGIS with PostgreSQL
7.5 in order to improve the statistics code to make use of some new
functionality - I think strk put the relevant changes into the CVS code.
I haven't used a 7.5/PostGIS combo for a couple of months but can't
think of any recent changes that would break anything.


Hope this helps,

Mark.

---

Mark Cave-Ayland
Webbased Ltd.
Tamar Science Park
Derriford
Plymouth
PL6 8BX
England

Tel: +44 (0)1752 764445
Fax: +44 (0)1752 764446


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 person.

> -----Original Message-----
> From: postgis-devel-bounces at postgis.refractions.net 
> [mailto:postgis-devel-bounces at postgis.refractions.net] On 
> Behalf Of Craig Miller
> Sent: 07 May 2004 08:07
> To: PostGIS Development Discussion
> Subject: RE: [postgis-devel] PostgreSQL 7.5 and PostGIS 0.8.1 or cvs
> 
> 
> Well, I didn't hear from anyone so I will see if I can find 
> some time to poke around tomorrow and figure out the problem.
> 
> --Craig
> 
> 
> -----Original Message-----
> From: Craig Miller [mailto:craig.miller at spatialminds.com]
> Sent: Thursday, May 06, 2004 2:11 PM
> To: postgis-devel at postgis.refractions.net
> Subject: [postgis-devel] PostgreSQL 7.5 and PostGIS 0.8.1 or cvs
> 
> 
> Hi,
> 
> I am trying to compile the unsupported combination of PostgreSQL 7.5
> (snapshot) and PostGIS 0.8.1 (or CVS).  I know this question 
> has come up before, but has anyone looked at the problem with 
> the call to canonicalize_qual and determined how the call 
> should be made to the version of this method included in pgsql 7.5?
> 
> The code:
>  /*
>          * If the index is partial, AND the index predicate with the
>          * explicitly given indexquals to produce a more 
> accurate idea of the
>          * index restriction.  This may produce redundant 
> clauses, which we
>          * hope that cnfify and clauselist_selectivity will deal with
>          * intelligently.
>          *
>          * Note that index->indpred and indexQuals are both 
> in implicit-AND form
>          * to start with, which we have to make explicit to hand to
>          * canonicalize_qual, and then we get back 
> implicit-AND form again.
>          */
>         if (index->indpred != NIL)
>         {
>                 Expr       *andedQuals;
> 
>                 andedQuals = 
> make_ands_explicit(nconc(listCopy(index->indpred),
> 
>           indexQuals));
>                 selectivityQuals = 
> canonicalize_qual(andedQuals, true);
>         }
> 
> 
> The error:
> 
> gcc -O2 -fno-strict-aliasing -Wall -Wmissing-prototypes 
> -Wmissing-declaratio
> ns -g -fexceptions   -I. -DFRONTEND 
> -DSYSCONFDIR='"/pgSpatial/etc/postgresql
> "'  -DUSE_VERSION=74  -I../../src/include 
> -I./src/include/port/win32 -DEXEC_ BACKEND  
> "-I../../src/include/port/win32"  -c -o postgis_estimate.o 
> postgis_estimate.c
> 
> postgis_estimate.c: In function `genericcostestimate2':
> postgis_estimate.c:751: too many arguments to function 
> `canonicalize_qual'
> postgis_estimate.c:751: warning: assignment from incompatible 
> pointer type
> make: *** [postgis_estimate.o] Error 1
> 
> Thanks for the help,
> --Craig
> 
> 
> _______________________________________________
> postgis-devel mailing list postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
> 
> 
> 
> 
> _______________________________________________
> postgis-devel mailing list postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel
>