Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvbru-006DsU-Qj for pgsql-admin@arkaria.postgresql.org; Wed, 25 Oct 2023 11:16:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qvbrt-002UcK-AB for pgsql-admin@arkaria.postgresql.org; Wed, 25 Oct 2023 11:16:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvbrr-002UcB-Tv for pgsql-admin@lists.postgresql.org; Wed, 25 Oct 2023 11:16:08 +0000 Received: from wout1-smtp.messagingengine.com ([64.147.123.24]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qvbrk-002ENy-Ld for pgsql-admin@lists.postgresql.org; Wed, 25 Oct 2023 11:16:06 +0000 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 4BE7E32009FA; Wed, 25 Oct 2023 07:15:58 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 25 Oct 2023 07:15:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1698232557; x= 1698318957; bh=nAzU9OHEtA0pELZ+VF4MvpTc946fTKKkt60xYgluUPU=; b=A clHERFbcGwBbH+t14gjAApr4f9gFxAu8cRZ5XqorMDCcScZm62bO48IQuqnrxvZG PvnZTTTksneaGHSrWGpmgvzEpYZLUAZqU3MV1TFJXX8cdPchYV+dQq7r+333OSpb XKy8eYE1AZqUol3X+48a/+UJK3pC+LqJnybBZB5Xgwt+et8PpasUhrTFHzrb0nl0 LTiDmcFae/ZB1bL9UsO3lh3Ot2oiQ59czVCavQDt/OLtLl6jMCfr1IX5xRiez06V wL2IVmLM2P1O30QFrI30qWdFHFdWHVzvplVoZfcyjWmHkGahd3zmpfWmor6P0nlc /HvVsap94Jj/2PnLS5+Zw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrledtgdefjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvfevuffkgggtugfgjgesthekre dttddtjeenucfhrhhomheptehlvhgrrhhoucfjvghrrhgvrhgruceorghlvhhhvghrrhgv segrlhhvhhdrnhhoqdhiphdrohhrgheqnecuggftrfgrthhtvghrnhepvdektdffudfftd ffffehfffhjeejhffgieeuueekjeekfffgudffhfduffffueevnecuffhomhgrihhnpegv nhhtvghrphhrihhsvggusgdrtghomhenucevlhhushhtvghrufhiiigvpedtnecurfgrrh grmhepmhgrihhlfhhrohhmpegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhg X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 25 Oct 2023 07:15:56 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1698232541; bh=nJju5XIiCSjLd8GC4knE00RRr7ZNky2HG5BXB0/LvuQ=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=eEMHLuIMzFBanMkY2ePDaVUbgP/En50WPmF/TVWzm0ORbjeaqNBEjTKWLFs060Vqz 7wdndfuMIAyxN0/1oSZ78Uul8+QZLuUTVXhbAvjvuFRhZuiDXgCCgsy/mYkvfiLYFS Cv7hqeDLJGxyD2qLxSK0wgDdm33XhTVLfZ5481I+UnzwJ6yYhzdqNtNsfsI41ew6H6 6jzuy45oFRW6mPrmkeOD66pf4+UF8pLreM+27A4enYZpehJMoxCn4s9sC4VZnbzJ9/ Uf3qVdcTLV8wDDhpHWQfVScwsEOLlB0Hc4Iq6qDD7ocQU8QBDdbm5F++B1Gntx+clR +fqEEWCegnv3A== Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B0D99E3; Wed, 25 Oct 2023 13:15:41 +0200 (CEST) Date: Wed, 25 Oct 2023 13:15:41 +0200 From: Alvaro Herrera To: Rajesh Kumar Cc: Pgsql-admin Subject: Re: Autovacuum and Insert wait Message-ID: <202310251115.5kpzzeujhwtn@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 2023-Oct-25, Rajesh Kumar wrote: > Can autovacuum cause insert wait? Yes, in unlucky situations. > I could see in log that there are lot of insert waiting for a table ...At > the same time autovacuum is running for table. Did you examine pg_locks and pg_stat_activity in detail to see what exactly was going on? It's easy to jump to wrong conclusions. -- Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/ "Aprender sin pensar es inútil; pensar sin aprender, peligroso" (Confucio)