Re: Tracing in Postgres

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Harshitha S <hershetha(at)gmail(dot)com>, pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Tracing in Postgres
Date: 2011-07-25 23:32:46
Message-ID: 4E2DFD1E.40208@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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-brainer.

--
Craig Ringer

POST Newspapers
276 Onslow Rd, Shenton Park
Ph: 08 9381 3088 Fax: 08 9388 2258
ABN: 50 008 917 717
http://www.postnewspapers.com.au/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Salisbury 2011-07-26 00:17:29 create table as select... with auto increment id ?
Previous Message Alexandre Savaris 2011-07-25 23:06:20 Error calling PG_RETURN_NULL()