Re: parsing pg_ident.conf - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: parsing pg_ident.conf
Date
Msg-id alpine.DEB.2.22.394.2011201548070.42321@pseudo
Whole thread Raw
In response to Re: parsing pg_ident.conf  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
>>> I noticed somewhat to my surprise as I was prepping the tests for the
>>> "match the whole DN" patch that pg_ident.conf is parsed using the same
>>> routines used for pg_hba.conf, and as a result the DN almost always
>>> needs to be quoted, because they almost all contain a comma e.g.
>>> "O=PGDG,OU=Testing". Even if we didn't break on commas we would probably
>>> need to quote most of them, because it's very common to include spaces
>
> Maybe we should add a comment at the top of the file about when quoting
> is needed.

Yes, that is a good place to point that out. Possibly it would also be 
worth to add something in 20.2, including an example?

-- 
Fabien.



pgsql-hackers by date:

Previous
From: David Steele
Date:
Subject: Re: Online verification of checksums
Next
From: Peter Eisentraut
Date:
Subject: Re: abstract Unix-domain sockets