Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.300.41.1.7\))
Subject: Re: row from index tuple
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CANzqJaCDSAEiJf__-T9SPeQaXvKJVFEKS9MGay0u0qxLBzSQTQ@mail.gmail.com>
Date: Wed, 4 Feb 2026 10:42:01 -0700
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7081A53B-B564-4B91-A3F3-F94C06B17BEC@elevated-dev.com>
References: <A3158AF1-F385-469F-8FBF-0CC1670688DC@elevated-dev.com>
 <CANzqJaCDSAEiJf__-T9SPeQaXvKJVFEKS9MGay0u0qxLBzSQTQ@mail.gmail.com>
To: Ron Johnson <ronljohnsonjr@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/7081A53B-B564-4B91-A3F3-F94C06B17BEC%40elevated-dev.com>
Precedence: bulk

> On Feb 4, 2026, at 10:23=E2=80=AFAM, Ron Johnson =
<ronljohnsonjr@gmail.com> wrote:
>=20
> When I see deadlocks, both records are in the log file.  You don't see =
them, there are "?" placeholders. something else?

I thought so, but it had been a long time, and at a different job.

So, these logs are piped into Splunk, and are not directly available. =
Splunk treats each log line as a separate entry, so searching on =
"deadlock" was not showing me what I expected. We found the information =
by catching one in pg_locks, and by searching on timestamp in splunk--at =
the same time actually, different people on the call...

Anyway, we figured out the upstream misconfiguration which was giving us =
duplicate records on different streams (coming from RabbitMQ).