[pgpool-hackers: 592] Re: pool_error and elog

[Muhammad Usama]

Yes after elog API, pool_debug, pool_log and pool_error functions are
depreciated, and should be replaces by the newer version. But because of so
many instances of pool_debug and friend functions, not all have been
replaced and needs to be replaced by the patch which imported the elog API.
However replacing the pool_debug and pool_log is very straight forward and
can be done in little time. but replacing the pool_error is
little trickier and will require little more time because of long jump in
elog(ERROR alters the code flow.
I can take up the task and replace pool_debug and pool_log in first go and
will try to do pool_error before 3.4.0

Thanks
Usama



On Wed, Jul 30, 2014 at 7:45 AM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> Hi Usama,
>
> After you incorporating elog family, I see there's no reason to use
> pool_debug, pool_log etc. anymore. However still pool_debug, pool_log
> remain in the code. I think we should remove pool_debug, pool_log
> calls by the time when pgpool-II 3.4.0 is released. What do you think?
>
> Best regards,
> --
> Tatsuo Ishii
> SRA OSS, Inc. Japan
> English: http://www.sraoss.co.jp/index_en.php
> Japanese:http://www.sraoss.co.jp
> _______________________________________________
> pgpool-hackers mailing list
> pgpool-hackers at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20140804/b092e6ca/attachment.html>