Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Date: 2022-09-15 01:19:41
Message-ID: fbea8c6f-415a-bad9-c3de-969c40d08a84@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers


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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2022-09-15 01:38:40 Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Previous Message Tom Lane 2022-09-14 22:41:07 pgsql: Use the terminology "WAL file" not "log file" more consistently.