Re: "unix_socket_directories" should be GUC_LIST_INPUT?
Ian Lawrence Barwick <barwick@gmail.com>
From: Ian Lawrence Barwick <barwick@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2020-10-23T03:23:28Z
Lists: pgsql-hackers
Attachments
- unix_socket_directories-guc_list_input.v2.patch (text/x-patch) patch v2
2020年10月23日(金) 12:12 Michael Paquier <michael@paquier.xyz>: > > On Fri, Oct 23, 2020 at 11:34:06AM +0900, Ian Lawrence Barwick wrote: > > Not that I've ever had to do this (or would want to do it on a production > > system), but this error message seems incorrect: > > > > postgres=# ALTER SYSTEM SET unix_socket_directories = > > '/tmp/sock1','/tmp/sock2'; > > ERROR: SET unix_socket_directories takes only one argument > > > > Trivial patch attached. > > I have never seen that case, but I think that you are right. Still, > that's not the end of it, see by yourself what the following command > generates with only your patch, which is fancy: > ALTER SYSTEM SET unix_socket_directories = '/tmp/sock1','/tmp/, sock2'; > > We need an extra GUC_LIST_QUOTE on top of what you are proposing. Ah yes, good point. Updated version attached. Regards Ian Barwick -- EnterpriseDB: https://www.enterprisedb.com
Commits
-
Add GUC_LIST_INPUT and GUC_LIST_QUOTE to unix_socket_directories
- a05dbf477b0e 14.0 landed