[pgpool-hackers: 3312] nextval,setval,nextval,setval

[Sebastiaan Mannem]

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 <mailto: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,



	 	
Sebastiaan Alexander Mannem
Senior Consultant
Anthony Fokkerweg 1
1059 CM Amsterdam, The Netherlands
T: +31 6 82521560
www.edbpostgres.com <http://www.edbpostgres.com/>

				

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: email_logo.png
Type: image/png
Size: 3472 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: social_rss.png
Type: image/png
Size: 549 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: social_fb.png
Type: image/png
Size: 295 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: social_tw.png
Type: image/png
Size: 403 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: social_li.png
Type: image/png
Size: 415 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: social_gp.png
Type: image/png
Size: 462 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190417/c4e29243/attachment-0011.png>