| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Mark Dilger <hornschnorter(at)gmail(dot)com>, Martijn van Oosterhout <kleptog(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: XID-wraparound hazards in LISTEN/NOTIFY |
| Date: | 2023-11-08 19:52:16 |
| Message-ID: | 750246.1699473136@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Sat, Nov 23, 2019 at 12:10:56PM -0500, Tom Lane wrote:
>>> It suddenly strikes me to worry that we have an XID wraparound hazard
>>> for entries in the notify queue.
> Is this still an open issue? Should it be a TODO item?
I don't think anyone's done anything about it, so yeah.
Realistically, if you've got NOTIFY messages that are going unread
for long enough to risk XID wraparound, your app is broken. So
maybe it'd be sufficient to discard messages that are old enough
to approach the wrap horizon. But still that's code that doesn't
exist.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-11-08 19:58:14 | Re: XX000: tuple concurrently deleted during DROP STATISTICS |
| Previous Message | Daniel Gustafsson | 2023-11-08 19:34:51 | Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features) |