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 3043210.1663205920@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-committers
Andrew Dunstan <andrew@dunslane.net> writes:
> 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.

Ugh.  I'll look into a fix tomorrow --- but my first instinct is
that pg_upgrade shouldn't be so dependent on the exact wording of
pg_controldata output.

            regards, tom lane



pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Use the terminology "WAL file" not "log file" more consistently.
Next
From: John Naylor
Date:
Subject: Re: pgsql: Move gramparse.h to src/backend/parser