Re: Bug #958: plperl notice server log

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "A(dot)Bhuvaneswaran" <bhuvansql(at)myrealbox(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #958: plperl notice server log
Date: 2003-04-29 13:49:12
Message-ID: 26141.1051624152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"A.Bhuvaneswaran" <bhuvansql(at)myrealbox(dot)com> writes:
> Fine and thank you very much. As you said, elog is sending the notice to
> client and server log immediately. But what stops print from flushing the
> output to server log file immediately?

stdout is fully buffered by default, on most platforms anyway ... if you
printed to stderr it'd act different ...

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gaetano Mendola 2003-04-30 17:05:06 Duplicate key after a vacuum
Previous Message pgsql-bugs 2003-04-29 07:00:58 Bug #960: Call from functions in plpgsql can't pass a row as parameter