Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
От | Tom Lane |
---|---|
Тема | Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24 |
Дата | |
Msg-id | 16671.1507645188@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24 (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
Ответы |
Re: [BUGS] BUG #14830: Missed NOTIFications, PostgreSQL 9.1.24
|
Список | pgsql-bugs |
Alvaro Herrera <alvherre@alvh.no-ip.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
В списке pgsql-bugs по дате отправления: