[pgpool-hackers: 3313] Re: nextval,setval,nextval,setval

[Tatsuo Ishii]

Sebastiaan,

Thank you for pointing it out. Apparently that was my mistake. I am
going to fix them.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

> Hi Hackers,
> Today I visited a customer of ours using PgPool, and I noticed that they had this in their configuration file:
> 
>     black_function_list = 'nextval,setval,nextval,setval'
> 
> I questioned them that there was no obvious way for this, but they reflected that question, since it is in the pgpool.conf.sample.
> I tracked it down to this commit:
> 
>     commit f907fe8fdab0aabd7636efe15bca93dd748289d0
>     Author: Tatsuo Ishii <ishii at postgresql.org>
>     Date:   Sun Aug 17 21:24:19 2014 +0900
> 
>         First cut of database_redirect_preference_list and app_name_redirect_preference_list implementation.
> 
>         These allow more fine control of load balancing by specifying database
>         name or application name. See [pgpool-hackers: 589] for more details.
> 
> And mainly this change:
> 
>     diff --git a/src/sample/pgpool.conf.sample b/src/sample/pgpool.conf.sample
>     index 1088270a..d8666813 100644
>     --- a/src/sample/pgpool.conf.sample
>     +++ b/src/sample/pgpool.conf.sample
>     @@ -292,11 +292,20 @@ white_function_list = ''
>                                         # Comma separated list of function names
>                                         # that don't write to database
>                                         # Regexp are accepted
>     -black_function_list = 'nextval,setval'
>     +black_function_list = 'nextval,setval,nextval,setval'
>                                         # Comma separated list of function names
>                                         # that write to database
>                                         # Regexp are accepted
> 
> Can anyone explain if this change is meant, and if so, elaborate on the exact purpose?
> Or maybe this is something to fix?
> 
> Please let me know if you might have any info, and if I can do anything to have this fixed for clarity (if it should)...
> Not the most prudent issue, but easily fixed, right?
> Thanks in advance,
>