Re: Bug #958: plperl notice server log

From: "A(dot)Bhuvaneswaran" <bhuvansql(at)myrealbox(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "A(dot)Bhuvaneswaran" <bhuvansql(at)myrealbox(dot)com>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug #958: plperl notice server log
Date: 2003-04-29 06:51:05
Message-ID: Pine.LNX.4.44.0304291218440.1047-100000@Bhuvan.bksys.co.in
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2003-04-29 07:00:58 Bug #960: Call from functions in plpgsql can't pass a row as parameter
Previous Message Tom Lane 2003-04-29 06:09:17 Re: Bug #958: plperl notice server log