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 1oIuIt-0005p7-Qm for pgsql-performance@arkaria.postgresql.org; Tue, 02 Aug 2022 15:59:31 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oIuIr-0000MC-Kq for pgsql-performance@arkaria.postgresql.org; Tue, 02 Aug 2022 15:59:29 +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 1oIuIr-0000M2-B8 for pgsql-performance@lists.postgresql.org; Tue, 02 Aug 2022 15:59:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oIuIl-0002xf-18 for pgsql-performance@lists.postgresql.org; Tue, 02 Aug 2022 15:59:28 +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 272FxLGD2519233; Tue, 2 Aug 2022 11:59:21 -0400 From: Tom Lane To: bruno da silva cc: pgsql-performance@lists.postgresql.org Subject: Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries In-reply-to: References: Comments: In-reply-to bruno da silva message dated "Tue, 02 Aug 2022 11:08:05 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2519231.1659455961.1@sss.pgh.pa.us> Date: Tue, 02 Aug 2022 11:59:21 -0400 Message-ID: <2519232.1659455961@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk bruno da silva writes: > After more investigation, we found that pgss_query_texts.stat of a size of > 2.2GB. and this deployment has a 32bit pg. Hm ... we've heard one previous report of pg_stat_statements' query text file getting unreasonably large, but it's not clear how that can come to be. Do you have a lot of especially long statements being tracked in the pg_stat_statements view? Are there any other signs of distress in the postmaster log, like complaints about being unable to write pgss_query_texts.stat? regards, tom lane