On 25/07/2011 9:54 PM, Tom Lane wrote:
Or just redirect postmaster's stderr to the target file, and don't even
bother with syslog ...
True. I was working on the assumption that the OP wanted to change the
output destination at runtime, but if that is not the case then a simple
redirect is a no
Craig Ringer writes:
> On 25/07/11 12:33, Harshitha S wrote:
>> But I just want to replace the implementation of the logging/tracing
>> in Postgres, so that the existing messages can be redirected to a
>> file, a USB etc.,
> OK. If you are running on Unix/Linux you can just tell your syslog
> dae
Please reply to the list, not just to me.
On 25/07/11 12:33, Harshitha S wrote:
> I want to retain all the error messages, error report that is used by
> Postgres.
> I don't intend to log any information extra other than what is
> provided by Postgres.
> But I just want to replace the implementati
On 22/07/2011 4:43 PM, Harshitha S wrote:
Hi,
I am trying to integrate a tracing framework in the Postgres code.
I need to know if elog.c under backend/utils/error is the place where
the changes can be made.
It depends: what exactly are the kinds of events you want to trace?
If you're looking
