Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue

From: "Matheus Alcantara" <matheusssilv97(at)gmail(dot)com>
To: "Rishu Bagga" <rishu(dot)postgres(at)gmail(dot)com>, "Arseniy Mukhin" <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com>
Cc: "Yura Sokolov" <y(dot)sokolov(at)postgrespro(dot)ru>, "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, "Daniil Davydov" <3danissimo(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, "Alexandra Wang" <alexandra(dot)wang(dot)oss(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Joel Jacobson" <joel(at)compiler(dot)org>
Subject: Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue
Date: 2025-09-05 10:45:32
Message-ID: DCKT0VWL4B34.N09V46RR5QV9@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu Sep 4, 2025 at 8:02 PM -03, Rishu Bagga wrote:
> On Thu, Sep 4, 2025 at 7:14 AM Arseniy Mukhin
> <arseniy(dot)mukhin(dot)dev(at)gmail(dot)com> wrote:
>
>> Interesting, have you shared your patch and results somewhere? IIUC
>> Tom's approach resolves this bug, because with it we have queue
>> entries produced by committed transactions only, so we don't need to
>> check their status and don't have dependency on clog.
>
> I was eventually able to get better numbers with the patch after using
> a substantial number of connections, so I have now posted it here. [1].
>
Thanks for sharing the patch! I'll reserve some time to test and review.

--
Matheus Alcantara

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2025-09-05 11:14:06 Re: Parallel Apply
Previous Message Matheus Alcantara 2025-09-05 10:44:11 Re: LISTEN/NOTIFY bug: VACUUM sets frozenxid past a xid in async queue