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

[Sebastiaan Mannem]

No problem,
Awesome, thanks!


Op do 18 apr. 2019 om 02:02 schreef Tatsuo Ishii <ishii at sraoss.co.jp>

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


[image: EDB Postgres] <http://www.enterprisedb.com/>
Sebastiaan Alexander Mannem
Senior Consultant
Anthony Fokkerweg 1
1059 CM Amsterdam, The Netherlands
<http://maps.google.com/maps?f=q&source=embed&hl=en&geocode=&q=Anthony+Fokkerweg+1+1059+CM+Amsterdam%2C+The+Netherlands&ie=UTF8&hq=&hnear=Anthony+Fokkerweg+1+1059+CM+Amsterdam%2C+The+Netherlands&iwloc=near>

T: +31 6 82521560 <+31682521560>
www.edbpostgres.com
[image: Blog Feed] <http://blogs.enterprisedb.com/> [image: Facebook]
<https://www.facebook.com/EnterpriseDB> [image: Twitter]
<https://twitter.com/EDBPostgres> [image: LinkedIn]
<https://www.linkedin.com/company/14958?trk=tyah> [image: Google+]
<https://plus.google.com/108046988421677398468>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20190418/f22da003/attachment.html>