Re: XID-wraparound hazards in LISTEN/NOTIFY

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 20:49:59
Message-ID: ZUv0d60t_wc85QzR@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 8, 2023 at 02:52:16PM -0500, Tom Lane wrote:
> 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.

Thanks, TODO added.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Only you can decide what is important to you.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2023-11-08 21:15:21 Re: max_parallel_workers question
Previous Message Tom Lane 2023-11-08 20:12:16 Re: POC PATCH: copy from ... exceptions to: (was Re: VLDB Features)