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 1tY9zW-004qcO-NT for pgsql-general@arkaria.postgresql.org; Wed, 15 Jan 2025 20:27:55 +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 1tY9zT-00Gza0-IL for pgsql-general@arkaria.postgresql.org; Wed, 15 Jan 2025 20:27:52 +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 1tY9zT-00GzZF-7m for pgsql-general@lists.postgresql.org; Wed, 15 Jan 2025 20:27:51 +0000 Received: from relay6-d.mail.gandi.net ([2001:4b98:dc4:8::226]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1tY9zQ-000afm-2U for pgsql-general@lists.postgresql.org; Wed, 15 Jan 2025 20:27:49 +0000 Received: by mail.gandi.net (Postfix) with ESMTPSA id 031FDC0002; Wed, 15 Jan 2025 20:27:41 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=vondra.me; s=gm1; t=1736972863; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=CdffE/1DYs17CcG0SI+EKa1UOjVh/amddw5P1kZ23Kk=; b=UMQ1Fh83xY31r/6jB38w5wulXil6WAEjNQQN+MAov2Y5Ddi54paAKHGOQAjc6+9JIds1uY U00rsVlZQ3e3JE4sNEWRjO/EhhNQnRPxqb+CpuvkOOUtSVoLEJ1+Z/ZPbawyV/3FZLJO1l YegMJIO+lHsS89u/hWfeqCU9IpLxpNHZ6wR7iQgaBQrohu9JSxZG5Wghi0RWSgMHfhlwjC G+VfnrLvpAWZMsmPEDxmuySsf6k1RJjBgVQZ2fdQ9vvBn/73MKX0AGOp2k4U/GKZq1ihc2 Eoki82Wq1KrsBnO91zZRPDUd8b2QP8/o8I7uVZoJPslK/O+g+dR7k9qLmWHvvg== Message-ID: <37ae75bc-6385-4e41-9a48-e03e7884bcf3@vondra.me> Date: Wed, 15 Jan 2025 21:27:41 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Data Out of Sync with Physical Streaming Replication To: Tim Gerber , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-GND-Sasl: tomas@vondra.me List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 1/15/25 19:50, Tim Gerber wrote: > Hi All, > >... > > Archive mode is on.   I ran pg_amcheck and everything came back clean. I > know synchronous replication is an option, but it feels like something > else is going on and would like to get to the bottom of it. > > Any ideas on what could be causing this?  I’m planning on turning on > data_checksums and running pg_checksums to see if any corruption is found. > No idea. If the storage has some issues (which is the only thing data checksums could catch, in some cases), then anything is possible. I think it'd be interesting to compare the tuples returned on primary vs. standby, including system columns etc. Ideally using pageinspect. That might tell you what exactly is the difference, and perhaps also say which XID to look at. regards -- Tomas Vondra