pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedFrom: Laurenz Albe <laurenz.albe@cybertec.at>
To: Bruce Momjian <bruce@momjian.us>
Cc: afripowered@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Second paragraph a little bit misleading
Date: Fri, 21 Feb 2025 22:42:44 +0100
Message-ID: <fdf1336573bad1fd4688d9faeed21de8de5246a9.camel@cybertec.at> (raw)
In-Reply-To: <Z7jAm5QSgzf0kRzy@momjian.us>
References: <173928241056.707.3989867022954178032@wrigleys.postgresql.org>
<Z7dak8fwxwezBhyh@momjian.us>
<43db6e44e5bc8c6f22eb439c8256f1e1bc135cf7.camel@cybertec.at>
<Z7hq4D_QMwR85DOO@momjian.us>
<ee89f8397eeceee32fc773e0a235d7f222988096.camel@cybertec.at>
<Z7jAm5QSgzf0kRzy@momjian.us>
On Fri, 2025-02-21 at 13:06 -0500, Bruce Momjian wrote:
> > Hmpf. The documentation should always be in sync with the code, right?
> > So I think it should be left alone in HEAD, and if the checksum change
> > gets reverted, your patch should be applied to HEAD.
>
> I see your point, and I now agree that the "Reliability" section was
> just overlooked when the data checksum default was changed. I made a
> larger patch which improved the wording of data checksum mentions now
> that it is the default in master.
>
> I also fixed the Felix-reported problem in all the back branches through
> 14 --- PG 13 did not have the problem.
>
> Patches attached.
Thanks! These patches look good to me.
Yours,
Laurenz Albe
--
*E-Mail Disclaimer*
Der Inhalt dieser E-Mail ist ausschliesslich fuer den
bezeichneten Adressaten bestimmt. Wenn Sie nicht der vorgesehene Adressat
dieser E-Mail oder dessen Vertreter sein sollten, so beachten Sie bitte,
dass jede Form der Kenntnisnahme, Veroeffentlichung, Vervielfaeltigung oder
Weitergabe des Inhalts dieser E-Mail unzulaessig ist. Wir bitten Sie, sich
in diesem Fall mit dem Absender der E-Mail in Verbindung zu setzen.
*CONFIDENTIALITY NOTICE & DISCLAIMER
*This message and any attachment are
confidential and may be privileged or otherwise protected from disclosure
and solely for the use of the person(s) or entity to whom it is intended.
If you have received this message in error and are not the intended
recipient, please notify the sender immediately and delete this message and
any attachment from your system. If you are not the intended recipient, be
advised that any use of this message is prohibited and may be unlawful, and
you must not copy this message or attachment or disclose the contents to
any other person.
view thread (7+ messages)
Message-ID: <fdf1336573bad1fd4688d9faeed21de8de5246a9.camel@cybertec.at>
Permalink: ../fdf1336573bad1fd4688d9faeed21de8de5246a9.camel@cybertec.at/
Also on: postgresql.org/message-id/fdf1336573bad1fd4688d9faeed21de8de5246a9.camel@cybertec.at
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, bruce@momjian.us, afripowered@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: Second paragraph a little bit misleading
In-Reply-To: <fdf1336573bad1fd4688d9faeed21de8de5246a9.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox