Re: pg_xlog -> pg_xjournal?

From: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Joel Jacobson <joel(at)trustly(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_xlog -> pg_xjournal?
Date: 2015-06-01 03:50:59
Message-ID: 20150601035059.GA16424@toroid.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 2015-05-31 13:46:33 -0400, tgl(at)sss(dot)pgh(dot)pa(dot)us wrote:
>
> just always create pg_xlog as a symlink to pg_xjournal during initdb.

At first glance, the Subject: of this thread made me think that *was*
Joel's proposal. :-) But I think it's a great idea, and worth doing.

I think "pg_journal" (no "x") is sufficient. The journal is an idea that
people are familiar with from filesystems anyway.

> Note that we'd really also have to rename pg_clog etc

pg_clog could become pg_commits or pg_xactstatus or pg_commit_status or
something. What else is there? I'd hope pg_logical can be left alone.

> A more difficult question is whether we'd also rename pg_resetxlog,
> pg_receivexlog, etc.

I don't think it's necessary. (Of course, people have wanted to rename
pg_resetxlog to make it sound more scary anyway, but that's a different
matter.)

> In the end though, this is a lot of thrashing for a problem that
> only comes up rarely ...

I'll agree with Joel that it comes up far too often for comfort anyway.
I've known a number of people who were on the verge of deleting stuff
from pg_xlog, but just happened to check with me first.

-- Abhijit

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2015-06-01 04:46:11 Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
Previous Message Michael Paquier 2015-06-01 01:17:32 Re: [CORE] postpone next week's release