Re: row from index tuple

From: Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
To: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: row from index tuple
Date: 2026-02-04 17:42:01
Message-ID: 7081A53B-B564-4B91-A3F3-F94C06B17BEC@elevated-dev.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

> On Feb 4, 2026, at 10:23 AM, Ron Johnson <ronljohnsonjr(at)gmail(dot)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, 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).

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Scott Ribe 2026-02-10 16:55:55 debug a lockup
Previous Message Ron Johnson 2026-02-04 17:23:54 Re: row from index tuple