Re: Make pg_checksums complain if compiled BLCKSZ and data folder's block size differ
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Magnus Hagander <magnus@hagander.net>
Cc: Postgres hackers <pgsql-hackers@lists.postgresql.org>, Michael Banck <michael.banck@credativ.de>, Sergei Kornilov <sk@zsrv.org>
Date: 2019-03-17T09:10:45Z
Lists: pgsql-hackers
Attachments
- checksums-blcksz-error-v2.patch (text/x-diff) patch v2
On Sat, Mar 16, 2019 at 11:18:17AM +0100, Magnus Hagander wrote: > BLCKSZ is very much an internal term. The exposed name through pg_settings > is block_size, so I think the original was better. Combining that one with > yours into "initialized with block size %d" etc, makes it a lot nicer. Yes, what Fabien and you say here makes sense. > The "incompatible with pg_checksums" part may be a bit redundant with the > commandname at the start as well, as I now realized Fabien pointed out > downthread. But I would suggest just cutting it and saying "%s: database > files are incompatible" or maybe "%s: data directory is incompatible" even? "Cluster" is more consistent with the surroundings. So what about the attached then? -- Michael
Commits
-
Error out in pg_verify_checksums on incompatible block size
- 5864d246099f 11.3 landed
-
Error out in pg_checksums on incompatible block size
- fa3395659561 12.0 landed