Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24 - Mailing list pgsql-bugs

From Marko Tiikkaja
Subject Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
Date
Msg-id CAL9smLAQOMNzREjJy-M8kpqGOGYdub3wD1uPb38xeHHRN=TTZA@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24  (Marko Tiikkaja <marko@joh.to>)
Responses Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
List pgsql-bugs
So I managed to accidentally kill and/or restart both servers while trying to install debug symbols, but I'm doing a new run now and I noticed something interesting: the listening backend's RecentXmin doesn't seem to ever go forward.  By my reading of this code, that would mean trouble for this piece of code in TransactionIdIsInProgress:

  if (TransactionIdPrecedes(xid, RecentXmin))
      return false;

Is this not an obvious bug?  async.c would think the transaction is not running, and did not commit -> throw away the notification.  That would also explain why it takes days for this to happen (since we need to run through enough xids to wrap around).


.m

pgsql-bugs by date:

Previous
From: Giovanni Pisante | Danysoft
Date:
Subject: Re: [BUGS] please quote POSTGRESQL
Next
From: Petr Jelinek
Date:
Subject: Re: [BUGS] 10.0: Logical replication doesn't execute BEFORE UPDATE OF trigger