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

From Robert Haas
Subject Re: Renaming of pg_xlog and pg_clog
Date
Msg-id CA+TgmoY5bUx9qL1q=XwoGerQn0+BmhC4uQ0Mx-rUZqpQPG2qyg@mail.gmail.com
Whole thread Raw
In response to Re: Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Renaming of pg_xlog and pg_clog  (Stephen Frost <sfrost@snowman.net>)
Re: Renaming of pg_xlog and pg_clog  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Wed, Oct 12, 2016 at 10:22 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> OK. I can live with that as well. Attached are three patches. The
> pg_xlog -> pg_wal move, the pg_clog -> pg_transaction move, and the
> pg_clog -> pg_xact move. Only one survivor to be chosen among the last
> two ones.

Committed 0001.

To be honest, I don't really like either pg_transaction or pg_xact.
Neither name captures the fact that what we're really tracking here is
the transaction *status*.  pg_xact is slightly worse because it's a
poor abbreviation for transaction, but I think the argument against
even pg_transaction is similar to the one Tom previously levied
against pg_logical - viz. "logical what?".  The transaction themselves
are not stored in the directory, just the commit status.  The fact
that commit status is saved is the source of the "c" in "clog".

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: Indirect indexes
Next
From: Robert Haas
Date:
Subject: Re: Speed up Clog Access by increasing CLOG buffers