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 1siypN-00C9Ls-KR for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 16:13:53 +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 1siypL-009Nsk-K2 for pgsql-general@arkaria.postgresql.org; Tue, 27 Aug 2024 16:13:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1siypK-009Nsb-90 for pgsql-general@lists.postgresql.org; Tue, 27 Aug 2024 16:13:51 +0000 Received: from fout7-smtp.messagingengine.com ([103.168.172.150]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1siypG-001mZS-6F for pgsql-general@postgresql.org; Tue, 27 Aug 2024 16:13:50 +0000 Received: from phl-compute-01.internal (phl-compute-01.nyi.internal [10.202.2.41]) by mailfout.nyi.internal (Postfix) with ESMTP id 8899A138FF88; Tue, 27 Aug 2024 12:13:44 -0400 (EDT) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-01.internal (MEProxy); Tue, 27 Aug 2024 12:13:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1724775224; x=1724861624; bh=JX/LEXHT4115jmJia/yt0tGJ9UiIPxme/vXov/SVY5Y=; b= tC0pFhmiWnHKRlFZe2jIUhqOY+vojyJTeWGLjJOFIN1SOhGVdZxa3zGn5NRAA5V/ YsAK+5iIp7q3tVtVJG0+SAoeI06JnqTQZtkR8a97pyOzcOdtG9N24D+Q0lpW01ZL /x7Xi1ZVQ1PTgHTVmU12iRfIKsf2Ul0z7ek0MbyLvWpzkUhSbo3uOT7ObT0pFzSp j8E0Kalf0eaWhQHZVPvAEo5WyCVuFOKC/It4z70ux12Ny7n9g3UdVMng9qRjRA/i IF9klws4/jK7KzV6rD0hMeJKdOmFhVD8gRVa7oHzPcEFgNoC5vq3rWiDleRSITYo 1SRabGfq3VWugQcS2KHupA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1724775224; x= 1724861624; bh=JX/LEXHT4115jmJia/yt0tGJ9UiIPxme/vXov/SVY5Y=; b=O RaSVyjPC4L1OxzABhTJit45JS2JDQm5Zu/WO59xVTtIHcsy/yPQPMdBgvbKTjzM+ uzLzR2kWYRqCqErFweLTwfP2IlPwqhB5EXd+ZbMr6dbavKseh4Axf/celhKUnMK0 VLcMOyQw7SzsLIa+WRxgC6BO49Qn4GIToeNQaddYQ/8RuunuB8W5/hjCq4ihd2kS DAkHwlHUDCOv3VXu1BdTwR097TAqjIIVDfQk5woNObT2cHIwmyQDoO44jCFH3z92 cpK0M85q+DXP6q/DYZYHnmGHH1kQQfAVsJG6uOkDErHu+49Mtn+3f6PDHT15r3E2 mMbJj9K1Q/AkfLWYSvaJw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrudeftddgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnh htshculddquddttddmnecujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeen ucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrse grkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdev ieeluefhfedufeetkeejffekjeeujeehgeehgeektdenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomhdpnhgspg hrtghpthhtohepvddpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtoheprhgrmhdrmhgr uhhrhigrsehlrghvrghinhhtvghrnhgrthhiohhnrghlrdhinhdprhgtphhtthhopehpgh hsqhhlqdhgvghnvghrrghlsehpohhsthhgrhgvshhqlhdrohhrgh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 27 Aug 2024 12:13:43 -0400 (EDT) Message-ID: Date: Tue, 27 Aug 2024 09:13:43 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: After DB upgrade from PG13 to PG15 showing error To: Ram Pratap Maurya , "'pgsql-general@postgresql.org'" References: <5e94410e-ae0e-db88-24cc-58805a9f73d0@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/27/24 01:50, Ram Pratap Maurya wrote: > Dear Team, > > We have upgraded PostgreSQL DB from version 13 to 15 version . > > We are facing issue in PG15 we not enable any parameter related to > AUTOVACUUM , but still running on PG15 data base. You need to provide more detail about the above. What parameters are you trying to change? Do you get an error? Did you reload/restart the server after the changes? What user did you do the changes as? > *2024-08-26 00:00:36.783 IST [702937] WARNING:  oldest xmin is far in > the past* > > *2024-08-26 00:00:36.783 IST [702937] HINT:  Close open transactions > soon to avoid wraparound problems.* > > *        You might also need to commit or roll back old prepared > transactions, or drop stale replication slots.* I would say the above is pointing you at possible solutions. To understand why this is important: https://www.postgresql.org/docs/16/routine-vacuuming.html Read the following sections: 25.1.5. Preventing Transaction ID Wraparound Failures 25.1.6. The Autovacuum Daemon > > Regards, > > Ram Pratap. > -- Adrian Klaver adrian.klaver@aklaver.com