Re: row from index tuple - Mailing list pgsql-admin

From Scott Ribe
Subject Re: row from index tuple
Date
Msg-id 7081A53B-B564-4B91-A3F3-F94C06B17BEC@elevated-dev.com
Whole thread Raw
In response to Re: row from index tuple  (Ron Johnson <ronljohnsonjr@gmail.com>)
List pgsql-admin
> On Feb 4, 2026, at 10:23 AM, Ron Johnson <ronljohnsonjr@gmail.com> wrote:
>
> 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,
sosearching on "deadlock" was not showing me what I expected. We found the information by catching one in pg_locks, and
bysearching 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
fromRabbitMQ). 




pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Re: row from index tuple
Next
From: Scott Ribe
Date:
Subject: debug a lockup