Re: Bug #958: plperl notice server log - Mailing list pgsql-bugs

From A.Bhuvaneswaran
Subject Re: Bug #958: plperl notice server log
Date
Msg-id Pine.LNX.4.44.0304291218440.1047-100000@Bhuvan.bksys.co.in
Whole thread Raw
In response to Re: Bug #958: plperl notice server log  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Bug #958: plperl notice server log  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>
> Printing to stdout is not the defined way to send a notice to a Postgres
> client.  Use elog:
> http://www.ca.postgresql.org/users-lounge/docs/7.3/postgres/plperl-database.html

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?

regards,
bhuvaneswaran

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug #958: plperl notice server log
Next
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #960: Call from functions in plpgsql can't pass a row as parameter