From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: parsing pg_ident.conf |
Date: | 2020-11-20 14:54:24 |
Message-ID: | alpine.DEB.2.22.394.2011201548070.42321@pseudo |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-11-20 15:06:43 | Re: abstract Unix-domain sockets |
Previous Message | David Steele | 2020-11-20 14:50:33 | Re: Online verification of checksums |