Re: More issues with pg_verify_checksums and checksum verification in base backups
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Stephen Frost <sfrost@snowman.net>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>, Andres Freund <andres@anarazel.de>, Andrew Dunstan <andrew@dunslane.net>, Daniel Gustafsson <daniel@yesql.se>, Magnus Hagander <magnus@hagander.net>, Tom Lane <tgl@sss.pgh.pa.us>
Date: 2018-10-24T05:31:37Z
Lists: pgsql-hackers
On Sun, Oct 21, 2018 at 08:56:32PM -0400, Stephen Frost wrote: > All of this pie-in-the-sky about what pluggable storage might have is > just hand-waving, in my opinion, and not worth much more than that. I > hope (and suspect..) that the actual pluggable storage that's being > worked on doesn't do any of this "just drop a file somewhere" because > there's a lot of downsides to it- and if it did, it wouldn't be much > more than what we can do with an FDW, so why go through and add it? Well, there is no point in enforcing a rule that something is forbidden if if was never implied and never documented (the rule here is to be able to drop custom files into global/, base/ or pg_tblspc.). Postgres is highly-customizable, I would prefer if features in core are designed so as we keep things extensible, the checksum verification for base backup on the contrary restricts things. So, do we have other opinions about this thread? -- Michael
Commits
-
Fix various checksum check problems for pg_verify_checksums and base backups
- 19516afdf167 11.2 landed
- 5c995139752f 12.0 landed
-
Switch pg_verify_checksums back to a blacklist
- 85036308dc58 11.2 landed
- a1c91dd1108c 12.0 landed