Re: filenames in pg_basebackup - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: filenames in pg_basebackup
Date
Msg-id 1343254661-sup-290@alvh.no-ip.org
Whole thread Raw
In response to Re: filenames in pg_basebackup  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: filenames in pg_basebackup
Re: filenames in pg_basebackup
List pgsql-hackers
Excerpts from Tom Lane's message of mié jul 25 16:25:36 -0400 2012:
> Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> > Apparently, this needs a thorough revision ...
>
> Evidently.  Peter tends to see to that sort of thing while he works on
> translations, but I'm sure he wouldn't mind some help.

Here's an attempt at that.

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.

--
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: tuplesort memory usage: grow_memtuples
Next
From: Tom Lane
Date:
Subject: Re: filenames in pg_basebackup