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 <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1oJG7W-0007uZ-N3
	for pgsql-performance@arkaria.postgresql.org; Wed, 03 Aug 2022 15:17:14 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-performance-owner+archive@lists.postgresql.org>)
	id 1oJG7S-0002g8-LM
	for pgsql-performance@arkaria.postgresql.org; Wed, 03 Aug 2022 15:17:10 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oJG7S-0002fu-BB
	for pgsql-performance@lists.postgresql.org; Wed, 03 Aug 2022 15:17:10 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1oJG7P-00061K-VZ
	for pgsql-performance@lists.postgresql.org; Wed, 03 Aug 2022 15:17:09 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 273FH53F3041345;
	Wed, 3 Aug 2022 11:17:05 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: bruno da silva <brunogiovs@gmail.com>
cc: pgsql-performance@lists.postgresql.org
Subject: Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries
In-reply-to: 
 <CAB+Nuk-Pfyvb7bo4MrDjA_vymEd=aOMJO274QZsQRx08aDx5VQ@mail.gmail.com>
References: 
 <CAB+Nuk93fL1Q9eLOCotvLP07g7RAv4vbdrkm0cVQohDVMpAb9A@mail.gmail.com>
 <CAB+Nuk8BT4nroR+AWvka=a9qQxLEfByDC0tNbhY5mG4oaCzwBw@mail.gmail.com>
 <2519232.1659455961@sss.pgh.pa.us>
 <CAB+Nuk9_xmFc0js-JCOiUqQJL978FA4udD4yr4b9ha=3bUj59g@mail.gmail.com>
 <2659868.1659461133@sss.pgh.pa.us> <2680918.1659467679@sss.pgh.pa.us>
 <CAB+Nuk-Pfyvb7bo4MrDjA_vymEd=aOMJO274QZsQRx08aDx5VQ@mail.gmail.com>
Comments: In-reply-to bruno da silva <brunogiovs@gmail.com>
	message dated "Wed, 03 Aug 2022 11:12:49 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3041343.1659539825.1@sss.pgh.pa.us>
Date: Wed, 03 Aug 2022 11:17:05 -0400
Message-ID: <3041344.1659539825@sss.pgh.pa.us>
List-Id: <pgsql-performance.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-performance@lists.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-performance>
Archived-At: 
 <https://www.postgresql.org/message-id/3041344.1659539825%40sss.pgh.pa.us>
Precedence: bulk

bruno da silva <brunogiovs@gmail.com> writes:
> *Question: *Besides the gc issue that you mentioned, having a large ( 700MB
> or 1GB ) pgss_query_texts.stat could cause slowness in pg_stat_statement
> processing
> than leading to slower query responses with a 32bit PG? I'm thinking in
> reducing pg_stat_statements.max from 10k to 3k

Whether or not we've fully identified the problem, I think cutting
pg_stat_statements.max is a good idea.  Especially as long as you're
stuck on an unsupported PG version.

			regards, tom lane