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

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 09:24:20
Message-ID: 20220915092420.5helrihxjx3hzqid@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 2022-Sep-15, Tom Lane wrote:

> Yeah, the lowest-tech solution is to accept either spelling of
> the description string. But I'm not very happy with the whole
> approach right now. We should have an implementation that isn't
> dependent on how user-friendly strings are spelled.

We already discussed this, a mere 12 years ago,
https://postgr.es/m/1283373680-sup-9235@alvh.no-ip.org
for exactly the same reason.

Let's just do it?

--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Y una voz del caos me habló y me dijo
"Sonríe y sé feliz, podría ser peor".
Y sonreí. Y fui feliz.
Y fue peor.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Joe Conway 2022-09-15 10:12:40 Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Previous Message Andres Freund 2022-09-15 04:50:07 Re: pgsql: Move gramparse.h to src/backend/parser