Re: More issues with pg_verify_checksums and checksum verificationin base backups - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: More issues with pg_verify_checksums and checksum verificationin base backups
Date
Msg-id 20181024053137.GL1658@paquier.xyz
Whole thread Raw
In response to Re: More issues with pg_verify_checksums and checksum verificationin base backups  (Stephen Frost <sfrost@snowman.net>)
Responses Re: More issues with pg_verify_checksums and checksum verificationin base backups  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
List 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

Attachment

pgsql-hackers by date:

Previous
From: Kuntal Ghosh
Date:
Subject: Re: Unordered wait event ClogGroupUpdate
Next
From: Michael Paquier
Date:
Subject: Re: Unordered wait event ClogGroupUpdate