| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, 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 14:19:48 |
| Message-ID: | 16671.1507645188@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Tom Lane wrote:
>> 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?
> I think it's not totally unreasonable to have processes sitting idle for
> long periods of time.
Sure, but if they're truly idle, they aren't looking at RecentXmin ;-)
> Would they not recompute RecentXmin if they did a
> sinval reset?
Not sure, but if not, maybe making that code path update it would be
a suitable fix in practice? I'm a bit hesitant to put a GetSnapshotData
call into ProcessIncomingNotify, because of the possibility of adding a
lot of contention on the ProcArray if there's very heavy notify traffic.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Дилян Палаузов | 2017-10-10 14:31:40 | ./configure error: Cannot find a working 64-bit integer type |
| Previous Message | John McKown | 2017-10-10 14:19:17 | Re: please quote POSTGRESQL |