Re: filenames in pg_basebackup - Mailing list pgsql-hackers

From Tom Lane
Subject Re: filenames in pg_basebackup
Date
Msg-id 6235.1343258134@sss.pgh.pa.us
Whole thread Raw
In response to Re: filenames in pg_basebackup  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> One thing I'm not clear about is the "WAL file" vs "transaction log
> file" terminology.  We use both in various error messages.  Do we want
> to consistently use one?  It seems to me that we're using the very
> verbose "transaction log" phrase just to avoid exposing users to the
> "WAL" acronym, but that's probably a lost cause.  We also have the issue
> of calling those files "files" or "segments".  I understand that
> internally we don't want to confuse them, but I don't see that the
> distinction makes any sense to users.

Yeah, we did talk about that a bit when Heikki was working on the
64-bit-XLogPointer changes.  AFAIR, there was general consensus that
it'd be better to standardize on one terminology, but little agreement
on which wording to use :-(.  I'd say review the thread and pick one.
He who does the work gets to make the decision.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: filenames in pg_basebackup
Next
From: Alvaro Herrera
Date:
Subject: Re: filenames in pg_basebackup