Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAfxx-0006h8-HV for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 22:31:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAfxw-0007QM-EJ for pgsql-hackers@arkaria.postgresql.org; Thu, 20 Jan 2022 22:31:36 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAfxv-0007QD-EC for pgsql-hackers@lists.postgresql.org; Thu, 20 Jan 2022 22:31:36 +0000 Received: from us-smtp-delivery-117.mimecast.com ([170.10.133.117]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAfxr-0003pe-Qs for pgsql-hackers@lists.postgresql.org; Thu, 20 Jan 2022 22:31:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=clackamas.us; s=mimecast20210408; t=1642717890; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=JiqgvMPaxV6PXZiw36n+NGyPajkqJkTZVBbXi7o7Zkg=; b=b7k1c55gJjsNqUc7QrFyYRH8CeCU/GgnBb//M2nkYZCUpE59iEvwIjDneOBDUJfw16xF3X xJWMv7nMFmRQ8RUXhpg4V+JXif9ObH9zvj97Az+sk+CXrNvK2pezDsON6A9ORF10jYn1Xf fC5h5NFo1ggp5m92arYUFWowSqryrPw= Received: from GCC02-DM3-obe.outbound.protection.outlook.com (mail-dm3gcc02lp2104.outbound.protection.outlook.com [104.47.65.104]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-436-lRW7OMgQOkWPflPWNCtoig-1; Thu, 20 Jan 2022 17:31:18 -0500 X-MC-Unique: lRW7OMgQOkWPflPWNCtoig-1 Received: from BN3PR09CA0046.namprd09.prod.outlook.com (2603:10b6:400:3::14) by PH0PR09MB8028.namprd09.prod.outlook.com (2603:10b6:510:65::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.10; Thu, 20 Jan 2022 22:31:16 +0000 Received: from DM3GCC02FT033.eop-gcc02.prod.protection.outlook.com (2a01:111:f400:7d04::208) by BN3PR09CA0046.outlook.office365.com (2603:10b6:400:3::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4909.7 via Frontend Transport; Thu, 20 Jan 2022 22:31:16 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 198.245.132.32) smtp.mailfrom=clackamas.us; dkim=none (message not signed) header.d=none;dmarc=pass action=none header.from=clackamas.us Received: from Exch01.county.ds.clackamas.us (198.245.132.32) by DM3GCC02FT033.mail.protection.outlook.com (10.97.8.212) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4888.11 via Frontend Transport; Thu, 20 Jan 2022 22:31:16 +0000 Received: from Exch01.county.ds.clackamas.us (10.32.2.129) by Exch01.county.ds.clackamas.us (10.32.2.129) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.858.5; Thu, 20 Jan 2022 14:31:15 -0800 Received: from Exch01.county.ds.clackamas.us ([fe80::4cf8:d71:78c5:f7]) by Exch01.county.ds.clackamas.us ([fe80::4cf8:d71:78c5:f7%7]) with mapi id 15.02.0858.002; Thu, 20 Jan 2022 14:31:15 -0800 From: "Lugosi, Jim" To: "pgsql-hackers@lists.postgresql.org" Subject: Poor performance PostgreSQL13/PostGIS 3.x Thread-Topic: Poor performance PostgreSQL13/PostGIS 3.x Thread-Index: AdgOS8QTMwRl+hFvSvq6+q2D9L4wyw== Date: Thu, 20 Jan 2022 22:31:15 +0000 Message-ID: <792d4b48d5b2404cb1a521b25536eb49@clackamas.us> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.38.18.20] MIME-Version: 1.0 X-EOPAttributedMessage: 0 X-MS-PublicTrafficType: Email X-MS-Office365-Filtering-Correlation-Id: 3c064f76-ed47-42a3-da50-08d9dc64926d X-MS-TrafficTypeDiagnostic: PH0PR09MB8028:EE_ X-Microsoft-Antispam-PRVS: X-MS-Oob-TLC-OOBClassifiers: OLM:8882 X-MS-Exchange-SenderADCheck: 1 X-MS-Exchange-AntiSpam-Relay: 0 X-Microsoft-Antispam: BCL:0 X-Microsoft-Antispam-Message-Info: 1QoPltRNyCT8eeitBT3nDcnnqKvF3jCMSnQDNhtgnJWxA5BP+CHyMoe0d2K+cKEVn6rpyTtoSbRtS5nF89m8PiO5XhcEcx3WOpr3bQQRXvM/TIhJzFDmTah+rmSmE5FIpXsdFsVCFPut8Ha/yiJ4ieGeB938Pi/K5dTIFLaH1x4WeqsmbWcX7rX9XQjBsKnFI8FWqWVYyggFt1ZB9Xd1kgc2csdOsdH97eiijZjy+nv9Hr80BeWcwWG8bcegs78Av4l+i9DwBN1W1JEQR5ocDgW7u+awJ9THd+P5BZoFlDmvr2wSxFCwARxDHKny72P4EuoYQ9kE5Vy1Za2NP7fzlw+l+9A/lwuQzx8ft8JbROoNdzfnogM3Oltyy6Dtu462zFgx0Ppi3UwafscpVixrYYfdvETtd7EVaXmegvVE9M7B686vqRLrdlNE3jtvPdzkaffhffvAQhAkWneZ8BS8Tv3AeGjTk2leFsWUq4cw737lUHgMl6RVc30X69BwRzRTtGxw6olH5Hk1s5uj6OJZ43vIp20ckeM1pDITAzLfwjR22LjYJqlxVXaHoavXrELVqXaET4ry42cV1e77UWqbEXlSTqAnnAvK7ZWhU/Fkq9pP1dfq4ZlhrsKRbNtM9aRbYoNuysaQTBJ+DGrrR+8IMagl9xRNcYCVHtoNXOkDDYMP2M4BPfAlZr0ZSueO1npqutbNibXUuGwhssSym1Nu2W5u0frENd5Ml/f0O9ErzLrzUioiJoWt4mLq/GnU7pluwHgx0Pp4wOkTIFjynO7qfcHlPRJkHGghA5YNuKz67KBOpr5/xE3KbYXxnxjZLdn7uk2DmXPC/sJVLM2sJpFKASDCRj7i7z28fOiVhhOxXheTjtVtF/W5ltF1krIGzUjzwGJCy73xuiwh/vnz6MCqiCiBWeijCVEfLFlINm/gZsI= X-Forefront-Antispam-Report: CIP:198.245.132.32;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:Exch01.county.ds.clackamas.us;PTR:InfoDomainNonexistent;CAT:NONE;SFS:(4636009)(40470700002)(36840700001)(46966006)(81166007)(426003)(40460700001)(5660300002)(2616005)(86362001)(336012)(70206006)(83380400001)(356005)(36860700001)(82310400004)(508600001)(316002)(8676002)(186003)(26005)(8936002)(2906002)(70586007)(40140700001)(6916009)(7696005)(36756003)(24736004)(108616005)(47076005)(11771555001)(110056007)(80162009)(36900700001)(75396010);DIR:OUT;SFP:1102 X-OriginatorOrg: clackamas.us X-MS-Exchange-CrossTenant-OriginalArrivalTime: 20 Jan 2022 22:31:16.0055 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 3c064f76-ed47-42a3-da50-08d9dc64926d X-MS-Exchange-CrossTenant-Id: 11a5f385-e251-4bf1-b266-597e782882a0 X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=11a5f385-e251-4bf1-b266-597e782882a0;Ip=[198.245.132.32];Helo=[Exch01.county.ds.clackamas.us] X-MS-Exchange-CrossTenant-AuthSource: DM3GCC02FT033.eop-gcc02.prod.protection.outlook.com X-MS-Exchange-CrossTenant-AuthAs: Anonymous X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: PH0PR09MB8028 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA17A671 smtp.mailfrom=jimlug@clackamas.us X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: clackamas.us Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_792d4b48d5b2404cb1a521b25536eb49clackamasus_" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --_000_792d4b48d5b2404cb1a521b25536eb49clackamasus_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable Hi folks, We are struggling to figure out what is going on. We are migrating from Po= stgreSQL 9.6 to PostgreSQL 13 w/ PostGIS. Our 9.6 version was compiled fro= m source and the new version (13) was installed using Yum. BTW, the new ve= rsion is on a VM that has 16GB of memory, two cores, and 500 GB of disk. I= n 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 Postg= reSQL, the performance takes a big nose dive. We have being tweaking and t= uning the database and it appears to be happy but the response times from m= apfile 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), usi= ng pg_dump. Could this be causing issues? Should we load the data from sc= ratch? 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 app= ears that every map request sends the following query "SELECT PostGIS_Versi= on();", which in turn takes up a connection. Any suggestions would be greatly appreciated? __:) _ \<,_ (*)/ (*) James Lugosi Clackamas County GISP IS Software Specialist, Senior 121 Library Court, Oregon City OR 97045 503-723-4829 --_000_792d4b48d5b2404cb1a521b25536eb49clackamasus_ Content-Type: text/html; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable

Hi folks,

 

We are struggling to figure out what is going on.&nb= sp; 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 inst= alled using Yum.  BTW, the new version is on a VM that has 16GB of memory, two cores, and 500 GB of disk.  In addi= tion, we are using MapServer as our mapping engine and OpenLayers as the cl= ient side interface.  Once we switch over to the new version of Postgr= eSQL, 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.  Previo= usly, 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 P= ostGIS version.  It appears that every map request sends the following= query “SELECT PostGIS_Version();”, which in turn takes up a co= nnection.

 

Any suggestions would be greatly appreciated?  =

 

&nbs= p;    __J
   _ \<,_
  (*)/ (*)

James Lugosi

Clackamas County GISP

IS Software Specialist, Senior

121 Library Court, Oregon City OR 97045

503-723-4829

 

--_000_792d4b48d5b2404cb1a521b25536eb49clackamasus_--