Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Postgres scalability and performance on windows
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Gopal" <gopal(at)getmapping(dot)com>
- Cc: "Frank Wiles" <frank(at)wiles(dot)org>, "Guido Neitzer" <lists(at)event-s(dot)net>, pgsql-performance(at)postgresql(dot)org, postgis-users(at)postgis(dot)refractions(dot)net
- Subject: Re: Postgres scalability and performance on windows
- Date: Tue, 28 Nov 2006 11:24:42 -0500
"Gopal" <gopal(at)getmapping(dot)com> writes:
> This is the query and the schema....
> ...
> select
> sum(area(intersection(snaptogrid(chunkgeometry,0.00000001),
> GeometryFromText('POLYGON((-0.140030845589332
> 50.8208343077265,-0.138958398039148 50.8478005422809,-0.0963639712296823
> 50.8471133071392,-0.0974609286275892 50.8201477285483,-0.140030845589332
> 50.8208343077265))',4326))) * 100/ (0.00114901195862628)) as
> percentCover,
So evidently area(intersection(snaptogrid(...))) takes about 300
microsec per row. The PostGIS hackers would have to comment on whether
that seems out-of-line or not, and whether you can make it faster.
regards, tom lane
- Follow-Ups:
- Re: Postgres scalability and performance on windows
- From: J. Andrew Rogers
- Re: Postgres scalability and performance on windows
- References:
- Prev by Date: Re: Postgres scalability and performance on windows
- Next by Date: Re: Postgres scalability and performance on windows
- Previous by thread: Re: Postgres scalability and performance on windows
- Next by thread: Re: Postgres scalability and performance on windows
- Indexes: