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 1rH4yE-000wRh-IP for pgsql-general@arkaria.postgresql.org; Sat, 23 Dec 2023 16:35:26 +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 1rH4yD-002qpv-7f for pgsql-general@arkaria.postgresql.org; Sat, 23 Dec 2023 16:35:25 +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 1rH4yC-002qpm-T3 for pgsql-general@lists.postgresql.org; Sat, 23 Dec 2023 16:35:24 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rH4y6-00BqTv-2R for pgsql-general@lists.postgresql.org; Sat, 23 Dec 2023 16:35:23 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 7DA6B5C00F1; Sat, 23 Dec 2023 11:35:17 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 23 Dec 2023 11:35:17 -0500 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=fm1; t=1703349317; x=1703435717; bh=W3lKxDvdz3/NwSXHHrjtoqQMhYnbfJas6K53bjwyJvw=; b= S21JndZ0aAbaPTwJ6++pSDEFwsGe902AF8CKafH/yUZBUHJ3VT3RIx0xpxIR5BpU wIeLCnv5X6cycjrF4NcijpQ3gtlUGZatYW9/tEuYgoibKzuQJsRPm9BXYjVtWiV4 hvcDJzYJhydTejCreS8M0bEtTeCQXLGZi2TmTgxOx6pWRmgKSvU/r2G2Eavl887T J9qCOqE/c6SB4g067fw/amW1nPSJYITn4bDnJf45b7uKzCcP+pc3qoSlqM+FCinh 3ruE2vwg9a0KZGkc2q8V6tRSp3scyDdJdc2JrOcRHD1lMqRp1cxTTIoUB+aAvvPQ lOphEw9RodJiDdMYHZutqw== 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=fm2; t=1703349317; x= 1703435717; bh=W3lKxDvdz3/NwSXHHrjtoqQMhYnbfJas6K53bjwyJvw=; b=M m8yt/NyX4+NSh7ZbpCH04sR3kUDXGplbrGiidLsh2oUTjMPI97oQiRAPUJ58U0OF X14GJTH9Mes28Y6hOIRJMLBr0AoXT6SHuC0dkjdgmm9rTdGCoh6SpHz/IAe3GNWQ 0PqYQOMmfttg/iFot9beUXAD1rXFPKtf7eCNyfifLFDNGbe/SQ0/d2k5Q8yaB9vF xe6Ssb+bdINjjIGA6J/cW5BRVbc/RpBZJan6gX7OVGfVqTOOtNyx17H06F13ft6J /r2T8lPpMo1n/EYc74SRhtAoJX95ELoZOtFMkLDxZHqAEda4fQrBJAkdNxrCOi1Q xWtEN1/LcsfHrg4jjGfdQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdduledgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeffleegieefgfevudehtdfhkeeutdffjeevgeffgeej vedthefgudeiteefheejheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 23 Dec 2023 11:35:16 -0500 (EST) Message-ID: Date: Sat, 23 Dec 2023 08:35:16 -0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Unable to start postgresql-14 Content-Language: en-US To: Johnathan Tiamoh , pgsql-general@lists.postgresql.org References: 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 12/22/23 22:48, Johnathan Tiamoh wrote: > Hello, > > I am able to start postgresql because of the below error. Please is > there any help > > User > You > FATAL:  xlog flush request 4392/164662F8 is not satisfied --- flushed > only to 4392/F000058 > > > UserYouFATAL:  xlog flush request 4392/164662F8 is not satisfied --- > flushed only to 4392/F000058 > More information needed: 1) Exact Postgres version e.g 14.x 2) Is it community version or fork? 3) What was the command you used to start the cluster? 4) Do you have replication/WAL archiving set up? -- Adrian Klaver adrian.klaver@aklaver.com