public inbox for [email protected]  

help / color / mirror / Atom feed

From: Scott Ribe <[email protected]>
To: Ron Johnson <[email protected]>
Cc: Pgsql-admin <[email protected]>
Subject: Re: row from index tuple
Date: Wed, 4 Feb 2026 10:42:01 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CANzqJaCDSAEiJf__-T9SPeQaXvKJVFEKS9MGay0u0qxLBzSQTQ@mail.gmail.com>
References: <[email protected]>
	<CANzqJaCDSAEiJf__-T9SPeQaXvKJVFEKS9MGay0u0qxLBzSQTQ@mail.gmail.com>

> On Feb 4, 2026, at 10:23 AM, Ron Johnson <[email protected]> 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).

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: row from index tuple
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox