Skip site navigation (1) Skip section navigation (2)

Re: Renaming of pg_xlog and pg_clog

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Craig Ringer <craig(dot)ringer(at)2ndquadrant(dot)com>
Cc: Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Subject: Re: Renaming of pg_xlog and pg_clog
Date: 2016-08-29 06:30:17
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Mon, Aug 29, 2016 at 2:36 PM, Craig Ringer
<craig(dot)ringer(at)2ndquadrant(dot)com> wrote:
> I don't care if it comes as part of some greater reorg or not but I'll be
> really annoyed if scope creep lands up killing the original proposal to just
> rename these dirs. I think that a simple rename should be done first. Then
> if some greater reorg is to be done it can be done shortly after. The only
> people that'll upset are folks tracking early 10.0 dev and they'll be aware
> it's coming.

Okay, so let's do it. Attached are two patches:
- 0001 renames pg_clog to pg_trans. I have let clog.c with its current
name, as well as its structures. That's the mechanical patch, the ony
interesting part being in pg_upgrade.
- 0002 renames pg_xlog to pg_wal.

Attachment: 0001-Rename-pg_clog-to-pg_trans.patch
Description: application/x-patch (34.4 KB)
Attachment: 0002-Rename-pg_xlog-to-pg_wal.patch
Description: application/x-patch (64.0 KB)

In response to


pgsql-hackers by date

Next:From: Fujii MasaoDate: 2016-08-29 06:52:24
Subject: Re: pg_xlogdump fails to handle WAL file with multi-page XLP_FIRST_IS_CONTRECORD data
Previous:From: Haribabu KommiDate: 2016-08-29 06:10:00
Subject: ecpg -? option doesn't work in windows

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group