pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedPoor performance PostgreSQL 13/ PostGIS 3.x
2+ messages / 2 participants
[nested] [flat]
* Poor performance PostgreSQL 13/ PostGIS 3.x
@ 2022-01-20 22:50 Lugosi, Jim <JimLug@clackamas.us>
0 siblings, 1 reply; 2+ messages in thread
From: Lugosi, Jim @ 2022-01-20 22:50 UTC (permalink / raw)
To: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
Hi folks,
We are struggling to figure out what is going on. We are migrating from PostgreSQL 9.6 to PostgreSQL 13 w/ PostGIS. Our 9.6 version was compiled from source and the new version (13) was installed using Yum. BTW, the new version is on a VM that has 16GB of memory, two cores, and 500 GB of disk. In addition, we are using MapServer as our mapping engine and OpenLayers as the client side interface. Once we switch over to the new version of PostgreSQL, the performance takes a big nose dive. We have being tweaking and tuning the database and it appears to be happy but the response times from mapfile requests are 3 -7 seconds. Previously, the response time was below a second.
Another point is that we populated the new database from the old (9.6), using pg_dump. Could this be causing issues? Should we load the data from scratch? We use ogr2ogr (GDAL) to help assist with loading of spatial data. Anyway, not really sure what the problem is.
Lastly, why am I seeing so many requests as to the PostGIS version. It appears that every map request sends the following query "SELECT PostGIS_Version();", which in turn takes up a connection.
Any help would be greatly appreciated.
Thanks
__:)
_ \<,_
(*)/ (*)
James Lugosi
Clackamas County GISP
IS Software Specialist, Senior
121 Library Court, Oregon City OR 97045
503-723-4829
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Poor performance PostgreSQL 13/ PostGIS 3.x
@ 2022-02-18 15:38 Merlin Moncure <mmoncure@gmail.com>
parent: Lugosi, Jim <JimLug@clackamas.us>
0 siblings, 0 replies; 2+ messages in thread
From: Merlin Moncure @ 2022-02-18 15:38 UTC (permalink / raw)
To: Lugosi, Jim <JimLug@clackamas.us>; +Cc: pgsql-performance@lists.postgresql.org <pgsql-performance@lists.postgresql.org>
On Thu, Jan 20, 2022 at 4:50 PM Lugosi, Jim <JimLug@clackamas.us> wrote:
>
> Hi folks,
>
>
>
> We are struggling to figure out what is going on. We are migrating from PostgreSQL 9.6 to PostgreSQL 13 w/ PostGIS. Our 9.6 version was compiled from source and the new version (13) was installed using Yum. BTW, the new version is on a VM that has 16GB of memory, two cores, and 500 GB of disk. In addition, we are using MapServer as our mapping engine and OpenLayers as the client side interface. Once we switch over to the new version of PostgreSQL, the performance takes a big nose dive. We have being tweaking and tuning the database and it appears to be happy but the response times from mapfile requests are 3 -7 seconds. Previously, the response time was below a second.
please post EXPLAIN ANALYZE for a query that you think is
underperforming. Ideally, we can also produce from legacy 9.6
equivalent.
merlin
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2022-02-18 15:38 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-20 22:50 Poor performance PostgreSQL 13/ PostGIS 3.x Lugosi, Jim <JimLug@clackamas.us>
2022-02-18 15:38 ` Merlin Moncure <mmoncure@gmail.com>
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