* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > I will do that right now, just have to know... what do you mean "\d > <table> output" and the exact queries you mean everything except the > "using unique" keywords which I believe are only for mapserver (they are > not SQL syntax right?).
What I'm referring to is the exact query that mapserver sends to the
database. If you turn on statement logging in your PostgreSQL backend
you should see the queries which are coming from mapserver showing up.
One of the big things is that mapserver should be at least adding a
bounding-box restriction...
Thanks,
Stephen
> Cheers,
> Francesco Pirotti
>
> > * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> >> Takes more than 5 seconds though to show in my mapserver image, around
> >> 36
> >> seconds...
> >
> > Please post the table definitions including indexes and whatnot (ie:
> > \d <table> output). Also, make sure your tables are 'ANALYZE'd.
> > Also, the mapserver .map file might help. If you could also turn on
> > statement logging in the PG backend and then take the *exact* queries
> > mapserver is running and run them using 'explain analyze' and posting
> > them here, that would be a great help.
> >
> > Thanks,
> >
> > Stephen
> > _______________________________________________
> > postgis-users mailing list
> > [email protected]
> > http://postgis.refractions.net/mailman/listinfo/postgis-users
> >
>
>
> _______________________________________________
> postgis-users mailing list
> [email protected]
> http://postgis.refractions.net/mailman/listinfo/postgis-users
signature.asc
Description: Digital signature
_______________________________________________ postgis-users mailing list [email protected] http://postgis.refractions.net/mailman/listinfo/postgis-users
