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

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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-27 20:50:16
Message-ID: CAN4CZFMzFAo4kjSxHB4n7P2PmZYhiOxr5KL-L7zKWUZWgzFUuQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> I had a look at this today and came up with the attached v2. Apart from some
> comment changes the main difference is that I placed the test in an already
> existing testfile to reduce the number of initdb's required, and added a test
> for the error message in the logfile.

Looks better than my version, I always forget that I should also keep
test execution time in mind.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Zsolt Parragi 2026-07-27 21:20:52 Re: REPACK (CONCURRENTLY) doesn't handle invalid indexes
Previous Message Robert Haas 2026-07-27 20:28:06 Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY