Обсуждение: row from index tuple
How can I get from an index tuple to the row? The situation is that we're seeing deadlocks on inserts, because two different sources are sending rows that have the sameunique constraint, when they should not be doing that. Would love to get to an example row to hunt this down further. -- Scott Ribe scott_ribe@elevated-dev.com https://www.linkedin.com/in/scottribe/
On Wed, Feb 4, 2026 at 11:09 AM Scott Ribe <scott_ribe@elevated-dev.com> wrote:
How can I get from an index tuple to the row?
The situation is that we're seeing deadlocks on inserts, because two different sources are sending rows that have the same unique constraint, when they should not be doing that. Would love to get to an example row to hunt this down further.
When I see deadlocks, both records are in the log file. You don't see them, there are "?" placeholders. something else?
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
> 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).