RE: subscriptionCheck failures on nightjar

Hayato Kuroda (Fujitsu) <kuroda.hayato@fujitsu.com>

From: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, Kuntal Ghosh <kuntalghosh.2007@gmail.com>, Michael Paquier <michael@paquier.xyz>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Thomas Munro <thomas.munro@enterprisedb.com>, 'Tom Lane' <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Date: 2026-04-13T05:01:22Z
Lists: pgsql-hackers
Hi hackers,

Sorry for reviving the old thread. While digging threads related with
the recent BF failure [1] I found here. And same issues were reported
like [2] and [3], everything happened on the Windows platform.

Per my quick lookup of this thread, the issue could not happen if rename()
works atomically. I'm not sure for Windows env, but does it mean We do not use
atomic renaming on them?

[1]: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=drongo&dt=2026-04-12%2003%3A43%3A28
[2]: https://www.postgresql.org/message-id/flat/17989-6b9f058bad9cd31b%40postgresql.org
[3]: https://www.postgresql.org/message-id/flat/18638-760882b4e5851b71%40postgresql.org

Best regards,
Hayato Kuroda
FUJITSU LIMITED 




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Fix "base" snapshot handling in logical decoding