[HACKERS] renaming "transaction log" - Mailing list pgsql-hackers

From Peter Eisentraut
Subject [HACKERS] renaming "transaction log"
Date
Msg-id 89ba433e-8990-0aad-238f-55e1d7280ece@2ndquadrant.com
Whole thread Raw
Responses Re: [HACKERS] renaming "transaction log"  (Stephen Frost <sfrost@snowman.net>)
Re: [HACKERS] renaming "transaction log"  (David Steele <david@pgmasters.net>)
Re: [HACKERS] renaming "transaction log"  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] renaming "transaction log"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Most documentation and error messages still uses the term "transaction
log" to refer to the write-ahead log.  Here is a patch to rename that,
which I think should be done, to match the xlog -> wal renaming in APIs.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Bug in prepared statement cache invalidation?
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] transition table behavior with inheritance appearsbroken (was: Declarative partitioning - another take)