> On 23 Jan 2018, at 22:04, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> > wrote: > > On 1/23/18 14:59, Daniel Gustafsson wrote: >> It’s not specific to the implementation per se, but it increases the >> likelyhood >> of hitting it. In order to load certificates from Keychains the cert common >> name must be specified in the connstr, when importing the testfiles into >> keychains I ran into it for example src/test/ssl/client_ca.config. > > The change is > > - 'psql', '-X', '-A', '-t', '-c', "SELECT 'connected with $connstr'", > + 'psql', '-X', '-A', '-t', '-c', "SELECT \$\$connected with $connstr\$\$", > > So the problem must have been a single quote in the connstr.
Right, looking back at b5e2b87d-3e8a-4597-9a7f-8489b3b67...@yesql.se I realized I was misremembering, the issue was that I had sslcert:'keychain:common name’ parameters to encapsulate the whitespace into a string value. Sorry about that. > That can surely happen, but then so can having a $$. So without a > concrete example, I'm not sure how to proceed. Awaiting with this until the discussion on how to handle configuration and parameter per SSL implementation lands is probably best. cheers ./daniel
