| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Karl O(dot) Pinc" <kop(at)meme(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Patch to implement pg_current_logfile() function |
| Date: | 2017-01-18 20:52:36 |
| Message-ID: | CA+TgmobsBqGOD9-FodarKFoafbS3vUEfV-_ouHnuNFi6m5OuDg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 18, 2017 at 12:08 PM, Karl O. Pinc <kop(at)meme(dot)com> wrote:
> Seems to me that the file format should
> be documented if there's any intention that the end user
> look at or otherwise use the file's content.
>
> It's fine with me if the content of current_logfiles
> is supposed to be internal to PG and not exposed
> to the end user. I'm writing to make sure that
> this is a considered decision.
On the whole, documenting it seems better than documenting it,
provided there's a logical place to include it in the existing
documentation.
But, anyway, Michael shouldn't remove it without some explanation or discussion.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-01-18 20:59:01 | Re: Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
| Previous Message | Robert Haas | 2017-01-18 20:51:06 | Re: Patch to implement pg_current_logfile() function |