Race between datachecksum enablement and create table with the file_copy strategy

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Race between datachecksum enablement and create table with the file_copy strategy
Date: 2026-07-21 10:55:11
Message-ID: CAN4CZFPEBsz8JeY4ixQ1V4ZL_xOY6pJaZS8ZLGH7R+wF--pEtg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello

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.

See the attached patch and test case using a new injection point.

Attachment Content-Type Size
0001-createdb-recheck-checksum-state-before-file_copy.patch application/octet-stream 6.1 KB

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Vik Fearing 2026-07-21 14:28:20 Re: BUG #19563: Planner does not eliminate redundant outer DISTINCT over UNION
Previous Message PG Bug reporting form 2026-07-21 10:46:44 BUG #19563: Planner does not eliminate redundant outer DISTINCT over UNION