pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade
3+ messages / 3 participants
[nested] [flat]

* query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade
@ 2007-05-15 19:49 Jessica Richard <rjessil@yahoo.com>
  2007-05-16 00:54 ` Re: query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade Jim C. Nasby <decibel@decibel.org>
  2007-05-16 19:12 ` Re: query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 2 replies; 3+ messages in thread

From: Jessica Richard @ 2007-05-15 19:49 UTC (permalink / raw)
  To: pgsql-admin

We had the following upgrades last week:

proj-4.4.9 to proj-4.5.0
geos-2.2.1 to geos-2.2.3
Postgis 1.1.1 to Postgis 1.2.1,
then
Postgres 8.1.4 to 8.2.4


After the entire upgrades, a same query with geospatial functions that used to come back in a few minutes, now take about 3 minutes to finish, no erors, just much slower than before.

Has any one seen this performance issue after the upgrade before?

Thanks a lot,
Jessica



       
---------------------------------
Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. 

^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade
  2007-05-15 19:49 query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade Jessica Richard <rjessil@yahoo.com>
@ 2007-05-16 00:54 ` Jim C. Nasby <decibel@decibel.org>
  1 sibling, 0 replies; 3+ messages in thread

From: Jim C. Nasby @ 2007-05-16 00:54 UTC (permalink / raw)
  To: Jessica Richard <rjessil@yahoo.com>; +Cc: pgsql-admin

On Tue, May 15, 2007 at 12:49:54PM -0700, Jessica Richard wrote:
> We had the following upgrades last week:
> 
> proj-4.4.9 to proj-4.5.0
> geos-2.2.1 to geos-2.2.3
> Postgis 1.1.1 to Postgis 1.2.1,
> then
> Postgres 8.1.4 to 8.2.4
> 
> 
> After the entire upgrades, a same query with geospatial functions that used to come back in a few minutes, now take about 3 minutes to finish, no erors, just much slower than before.
> 
> Has any one seen this performance issue after the upgrade before?

It can happen, yes. If it's a PostGIS-specific query I suggest you post
to the PostGIS list asking for help about it. If it's not
PostGIS-specific you should post the query and EXPLAIN ANALYZE output
from both versions to pgsql-performance.
-- 
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade
  2007-05-15 19:49 query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade Jessica Richard <rjessil@yahoo.com>
@ 2007-05-16 19:12 ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 3+ messages in thread

From: Tom Lane @ 2007-05-16 19:12 UTC (permalink / raw)
  To: Jessica Richard <rjessil@yahoo.com>; +Cc: pgsql-admin

Jessica Richard <rjessil@yahoo.com> writes:
> After the entire upgrades, a same query with geospatial functions that used to come back in a few minutes, now take about 3 minutes to finish, no erors, just much slower than before.

The standard first question is "did you remember to re-ANALYZE your
tables after reloading into the new database"?

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2007-05-16 19:12 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2007-05-15 19:49 query becomes much slower after Postgres 8.2.4 and Postgis 1.2.1 upgrade Jessica Richard <rjessil@yahoo.com>
2007-05-16 00:54 ` Jim C. Nasby <decibel@decibel.org>
2007-05-16 19:12 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox