| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Sergei Kornilov <sk(at)zsrv(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Offline enabling/disabling of data checksums |
| Date: | 2019-03-21 09:57:41 |
| Message-ID: | alpine.DEB.2.21.1903211047220.10347@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Anyway, as this stuff is very useful for upgrade scenarios
> a-la-pg_upgrade, for backup validation and as it does not produce false
> positives, I would really like to get something committed for v12 in its
> simplest form...
Fine with me, the detailed doc is not a showstopper and can be improved
later one.
> Are there any recommendations that people would like to add to the
> documentation?
For me, I just want at least a clear warning on potential risks.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evgeniy Efimkin | 2019-03-21 10:11:36 | Re: Special role for subscriptions |
| Previous Message | Fabien COELHO | 2019-03-21 07:17:32 | Re: Offline enabling/disabling of data checksums |