[pgpool-general: 8555] write_function_list in 4.2 - can we use separators?

[zam bak]

Hi

According to the docs, "write_function_list" in 4.2 is not "schema sensitive"
https://www.pgpool.net/docs/42/en/html/runtime-config-load-balancing.html#GUC-WRITE-FUNCTION-LIST

This is a change from 4.1  in which the same parameter (called
balc_function_list) was not "schema sensitive"
https://www.pgpool.net/docs/41/en/html/runtime-config-load-balancing.html#GUC-BLACK-FUNCTION-LIST

Since I have a long list of data modifying function prefixes and I
also have several schemas where they may exist the following now has
to be expanded:
write_function_list =
'currval,lastval,nextval,setval,convert_.*,create_.*,delete_.*,handle_.*,insert_.*,mark_.*,move_.*,process_.*,purge_.*,selsert_.*,update_.*,upgrade_.*
,merge_.*'

For example, "merge_.*" now has to be
"merge_.*,schema1.merge_.*,schema2.merge_.*,schema3.merge_.*"
This is going to be rather ....interesting... to manage...

My question is:
Can I use *spaces*, *tabs* and/or *newlines* to "break apart" this
config parameter so its easier to manage in pgpool.conf?
Something like following (but only with example for merge_ shown to
reduce verbosity):

write_function_list = 'currval, lastval, nextval, setval
,convert_.*
,create_.*
,delete_.*
,handle_.*
,insert_.*
,mark_.*
,move_.*
,process_.*
,purge_.*
,selsert_.*
,update_.*
,upgrade_.*
,merge_.*
,schema1.merge_.*
,schema2.merge_.*
,schema3.merge_.*
'

Thanks
Z