Re: BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Marko Tiikkaja <marko(at)joh(dot)to>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
Date: 2017-10-10 13:58:58
Message-ID: 15645.1507643938@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Marko Tiikkaja <marko(at)joh(dot)to> writes:
> 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;

Hmm ... I suppose it's possible that that happens if the listening
backend isn't executing any SQL commands but is just sitting.
While that might describe your test harness, does it describe any
real-world application?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2017-10-10 14:06:21 Re: BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
Previous Message Petr Jelinek 2017-10-10 13:25:14 Re: 10.0: Logical replication doesn't execute BEFORE UPDATE OF <columns> trigger