Re: Race between datachecksum enablement and create table with the file_copy strategy

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Race between datachecksum enablement and create table with the file_copy strategy
Date: 2026-07-21 18:35:44
Message-ID: 409E1470-5B4C-42A0-922C-84FCE75A6109@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


> On 21 Jul 2026, at 12:55, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:

> There's a small race window between enabling data checksums and
> creating a new database with the file_copy strategy:
>
> Create database checks for in progress data checksums before it
> inserts a new row into pg_database. If the data checksum worker starts
> in that window, it can miss the new database completely and skip
> generating its checksums.

Thanks for the report and patch, I am currently out of the office but will check and apply on Sunday or Monday when back home.

./daniel

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2026-07-21 18:54:46 Re: Race between datachecksum enablement and create table with the file_copy strategy
Previous Message Dilip Kumar 2026-07-21 15:44:28 Re: BUG #19519: REPACK can fail due to missing chunk for toast value