Re: Renaming of pg_xlog and pg_clog

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Renaming of pg_xlog and pg_clog
Date: 2017-03-17 14:03:08
Message-ID: CAB7nPqTu0y8uxbqXYjUObW9Oq4jnZxcPv_uTwstparBBjsrbQg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 17, 2017 at 10:58 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Fine! I've committed the pg_clog renaming, but I'd really like to
> draw the line here. I'm not going to commit the pg_subtrans ->
> pg_subxact naming and am -1 on anyone else doing so. I think that
> having the names of things in the code match what shows up in the file
> system is an awfully desirable property which we should preserve
> insofar as we can do so without compromising other goals. Not
> invalidating what users and DBAs think they know about how PostgreSQL
> works is a good thing, too; there are a lot more people who know
> something about the directory layout than will read this thread.

I'm cool with that, thanks for the commit.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Steele 2017-03-17 14:31:56 Re: PATCH: Make pg_stop_backup() archive wait optional
Previous Message Rushabh Lathia 2017-03-17 14:01:24 Re: wait events for disk I/O