Re: Renaming of pg_xlog and pg_clog - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id CAB7nPqSUE4Zp=W798ryj=PuD0d7Jwgj85drZ_ENS2RZ0=W6new@mail.gmail.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Craig Ringer <craig.ringer@2ndquadrant.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Mon, Aug 29, 2016 at 9:39 PM, Craig Ringer
<craig.ringer@2ndquadrant.com> wrote:
> Cool. I'll mark as waiting on author pending that.
>
> It'll be good to get this footgun put away.

OK, so done. I have put the renaming of pg_xlog to pg_wal on top patch
stack as that's the one making no discussion it seems: a lot of people
like pg_wal. I have added as well handling for the renaming in
pg_basebackup by using PQserverVersion. One thing to note is that a
connection needs to be made to the target server *before* creating the
soft link of pg_xlog/pg_wal because we need to know the version of the
target server. pg_upgrade is handled as well. And that's all in 0001.

Patch 0002 does pg_clog -> pg_trans, "trans" standing for
"transaction". Switching to pg_trans_status or pg_xact_status is not
that complicated to change anyway...
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Etsuro Fujita
Date:
Subject: Re: Odd oid-system-column handling in postgres_fdw
Next
From: Amit Kapila
Date:
Subject: Re: Write Ahead Logging for Hash Indexes