Excerpts from Tom Lane's message of mié jul 25 16:25:36 -0400 2012: > Alvaro Herrera <alvhe...@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 <alvhe...@commandprompt.com> The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support
pg_basebackup.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
