Re: pgsql: Use the terminology "WAL file" not "log file" more consistently. - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Date
Msg-id 3122568.1663217302@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-committers
Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com> writes:
> We seem to be maintaining old code in pg_upgrade to not break it, see
> [3]. I can think of a fix [4] or just [5], it may not be great to do
> these kinds of fixes for all the pg_resetwal output changes. Since the
> changes we make to the output formats of controlfile or pg_resetwal
> are very rare, any of [4] or [5] looks good to me and it is better
> than backporting [2] IMO.

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.  (git seems
a bit ahead of us here, with its distinction between "plumbing"
and "porcelain" operations.)

            regards, tom lane



pgsql-committers by date:

Previous
From: John Naylor
Date:
Subject: pgsql: Fix grammar in error message
Next
From: Andres Freund
Date:
Subject: Re: pgsql: Move gramparse.h to src/backend/parser