[pgpool-hackers: 2699] [Proposal] Implementing unix_socket_directories and friends
Tatsuo Ishii
ishii at sraoss.co.jp
Wed Jan 31 10:41:55 JST 2018
We have following in our TODO list:
https://pgpool.net/mediawiki/index.php/TODO#Support_multiple_UNIX_domain_socket_directories
As discussed in the URL (actually in a mail pointed by it), probably
just borrowing the idea from PostgreSQL is the best. If we are going
this direction, issues are:
1) How to migrate from socket_dir to unix_socket_directories?
I propose leaving socket_dir for 1 major release saying "we are
deprecating..." and treat it as if there's only one socket directory
in the unix_socket_directories. If unix_socket_directories is not
specified (not empty), then we take priority it over socket_dir.
2) unix_socket_group, and unix_socket_permissions
Do we want to implement them along with unix_socket_directories? My
opinion is "why not". We are going to borrow the implementation from
PostgreSQL anyway, so it would be easier to implement them along with
unix_socket_directories.
3) How to treat pcp_socket_dir?
One big question is whether we need separate pcp_socket_dir from
socket_dir at all. I think the answer is no, and we should unify it to
socket_dir and/or unix_socket_directories. Any objection?
Comments, suggestions are welcome.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
More information about the pgpool-hackers
mailing list