| From: | Vik Fearing <vik(at)2ndquadrant(dot)fr> |
|---|---|
| To: | 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: | 2016-11-02 00:01:16 |
| Message-ID: | 4ec0bcda-38dd-7297-7864-c547b99e5af5@2ndquadrant.fr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/09/2016 07:32 PM, Gilles Darold wrote:
> This patch implements the pg_current_logfile() function that can be
> used as follow. The function returns NULL when logging_collector
> is not active and outputs a warning.
I'm really late to this discussion, and I apologize for that; but I'm
wondering why we're doing all this through some random file on disk.
Why not just use the stats collector and have everything we'd want in a
pg_stat_logger view just like we have for pg_stat_archiver and others?
That makes the most sense to me.
We could then also count the number of rotations per time/size and whatnot.
--
Vik Fearing +33 6 46 75 15 36
http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kouhei Kaigai | 2016-11-02 00:31:29 | Re: Proposal: scan key push down to heap [WIP] |
| Previous Message | Fabien COELHO | 2016-11-01 22:46:13 | Re: Specifying the log file name of pgbench -l option |