From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Date: Wed, 14 Sep 2022 21:19:41 -0400
Message-ID: <fbea8c6f-415a-bad9-c3de-969c40d08a84@dunslane.net> (raw)
In-Reply-To: <E1oYb46-000N30-F2@gemulon.postgresql.org>
References: <E1oYb46-000N30-F2@gemulon.postgresql.org>
On 2022-09-14 We 18:41, Tom Lane wrote:
> Use the terminology "WAL file" not "log file" more consistently.
>
> Referring to the WAL as just "log" invites confusion with the
> postmaster log, so avoid doing that in docs and error messages.
> Also shorten "WAL segment file" to just "WAL file" in various
> places.
The pg_upgrade part of this seems seriously awry (see buildfarm animal
crake). We can't assume that the upgrade source is using the new wording.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-committers@postgresql.org
Cc: andrew@dunslane.net, tgl@sss.pgh.pa.us
Subject: Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
In-Reply-To: <fbea8c6f-415a-bad9-c3de-969c40d08a84@dunslane.net>
References: <E1oYb46-000N30-F2@gemulon.postgresql.org> <fbea8c6f-415a-bad9-c3de-969c40d08a84@dunslane.net>
* 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