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