Re: Patch to implement pg_current_logfile() function

From: Gilles Darold <gilles(dot)darold(at)dalibo(dot)com>
To: "Karl O(dot) Pinc" <kop(at)meme(dot)com>
Cc: Christoph Berg <myon(at)debian(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Shulgin, Oleksandr" <oleksandr(dot)shulgin(at)zalando(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch to implement pg_current_logfile() function
Date: 2016-10-28 08:03:37
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

Le 28/10/2016 à 05:09, Karl O. Pinc a écrit :
> Hi Gilles,
> On Thu, 27 Oct 2016 19:03:11 +0200
> Gilles Darold <gilles(dot)darold(at)dalibo(dot)com> wrote:
>> The current v8 of the patch
> For your consideration.
> Attached is a patch to apply to v8 of your patch.
> I moved the call to logfile_writename() in write_syslogger_file()
> into the open_csvlogfile(). That's where the new filename
> is generated and it makes sense to record the new name
> upon generation.

Yes, it make sense. The last change to documentation, comment and this
move have been included in the v9 of the patch, attached here.

Thanks a lot.

Gilles Darold
Consultant PostgreSQL -

Attachment Content-Type Size
patch_pg_current_logfile-v9.diff text/x-diff 12.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2016-10-28 08:53:36 Streaming basebackups vs pg_stat_tmp
Previous Message Amit Langote 2016-10-28 07:53:54 Re: Declarative partitioning - another take