Re: Patch to implement pg_current_logfile() function - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Patch to implement pg_current_logfile() function
Date
Msg-id CA+TgmoaZTxQaCB6Wx12fb4Hs4FTNuhTov7Lojmu9AU0nn+t21A@mail.gmail.com
Whole thread Raw
In response to Re: Patch to implement pg_current_logfile() function  ("Karl O. Pinc" <kop@meme.com>)
Responses Re: Patch to implement pg_current_logfile() function  (Gilles Darold <gilles.darold@dalibo.com>)
List pgsql-hackers
On Thu, Nov 3, 2016 at 7:34 PM, Karl O. Pinc <kop@meme.com> wrote:
> To me, the CURRENT_LOG_FILENAME symbol should contain the name
> of the current log file.  It does not.  The CURRENT_LOG_FILENAME symbol
> holds the name of the file which itself contains the name of
> the log file(s) being written, plus the log file
> structure of each log file.

I agree that this is confusing.

> IMO, the name of the log files being written, as well as
> the type of data structure written into each log file,
> are meta-information about the logging data.  So maybe
> the right name is LOG_METAINFO_DATAFILE.

+1 for something like this.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: SERIALIZABLE with parallel query
Next
From: Tom Lane
Date:
Subject: Re: pg_dump, pg_dumpall and data durability