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 1s4j36-000Z7H-Ps for pgsql-general@arkaria.postgresql.org; Wed, 08 May 2024 15:17:41 +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 1s4j35-001bSD-2J for pgsql-general@arkaria.postgresql.org; Wed, 08 May 2024 15:17:39 +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 1s4j33-001bPJ-5x for pgsql-general@lists.postgresql.org; Wed, 08 May 2024 15:17:39 +0000 Received: from wfout4-smtp.messagingengine.com ([64.147.123.147]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s4j30-0002IY-5R for pgsql-general@postgresql.org; Wed, 08 May 2024 15:17:36 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfout.west.internal (Postfix) with ESMTP id 814F31C000CE; Wed, 8 May 2024 11:17:31 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 08 May 2024 11:17:31 -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=fm2; t=1715181451; x=1715267851; bh=zBeL2T7FlaG0u9UgoRJC5QTYWcPWUd8an6PmlKU09p0=; b= Tl6EYUa2gYKlQgZyN0NuqffA/s1DFxi+JOiRMP+LvXsU4neAGCGdRdtstqEzituq +k9B6dY4Ln9BsWlyd4J/gPm/TMXgcKvib9uKLECr5mXRETD6nypJnV7xbP3TpDU5 z1RoEwCJ1XJKgvcWXzyUBvFPTN0u+mntduQf/ebor+rtGwZOrMEyhS+jLnvAUgeM HPnXqrrMYOyqQm5YIM1b/mJhNx+PnTmj7/hjKp5k3GGfKpXytFev+tPuUqPWmDe0 NdLPb3UhQWMfnn/s4SnFTXgcXRQBXDVDKtsXk2UJHa+OaQ4UHgw8otIC/RbupiZG wFGkei3Ta0uF8p38OV4cxA== 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=fm3; t=1715181451; x= 1715267851; bh=zBeL2T7FlaG0u9UgoRJC5QTYWcPWUd8an6PmlKU09p0=; b=T 5zUtUAdtIPfQ519eb42hpRVu6zUSmYQZnaZWNFyN834azsYLzNWHjxzya1sl6Nca nHRupJDde2zDIiLfdOWQn5Io5gUbsrhGK4iSSyw2V2yvtnY/Zi7R2IXZyzpNnD5C Kte8PlC5hRo74hZ4UMSzy+TKAFjnMYyRYZuKtK1Rx7xRBSjKJs8Yz/m8XB2UjSae 43T4prgrJQhCDEhyFsx8nmnBgG1H8u/NcugBeWiplAG0gzEidAPH9FOomiltOcdl Ns9nkUZvcDCo7Pb4rP7ZQJfsz8pHjrtzJvwJVFLTvbqCP9ONQdYisyxeCZO5TRxJ O43WOTHNmBmyD3q/DcuaA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeftddgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeffleegieefgfevudehtdfhkeeutdffjeevgeffgeej vedthefgudeiteefheejheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 8 May 2024 11:17:30 -0400 (EDT) Message-ID: <8a534c5f-e400-4bb5-b39e-2017d259ff06@aklaver.com> Date: Wed, 8 May 2024 08:17:29 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Unexpected data when subscribing to logical replication slot To: Daniel McKenzie , pgsql-general@postgresql.org References: 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 > > We have found two things that appear to resolve the problem - > > * Using a more powerful EC2 instance. We can reproduce the issue with > a r7a.medium instance but not with a r7a.large EC2 instance. > * Changing the Postgres synchronous_commit parameter from "on" to > "off". We cannot reproduce the issue with synchronous_commit set to > "off". What is running on the EC2 instance?: 1) The Postgres server. 2) The replication receiver. 3) Both. > > We need help to understand this unexpected behaviour. > > We are using Postgres 14.10. > > Thanks, > Daniel McKenzie -- Adrian Klaver adrian.klaver@aklaver.com