Re: get current log file

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Euler Taveira <euler(at)timbira(dot)com(dot)br>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Armor <yupengstone(at)qq(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: get current log file
Date: 2016-02-26 15:04:31
Message-ID: 32514.1456499071@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Euler Taveira <euler(at)timbira(dot)com(dot)br> writes:
> Those are good concerns. Also, we already have emit_log_hook that could
> grab server log messages. A small extension using the hook (there are
> some out there) could be use with a log consuming tool.

Hmmm ... emit_log_hook runs in the process calling elog, no? That would
not have any special visibility into the state of syslogger.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Konstantin Knizhnik 2016-02-26 15:05:55 Re: Relation cache invalidation on replica
Previous Message Euler Taveira 2016-02-26 15:02:03 Re: get current log file