| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | david(dot)zhang(at)highgo(dot)ca, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, postgresql(dot)org(at)coelho(dot)net |
| Subject: | Re: Allow continuations in "pg_hba.conf" files |
| Date: | 2020-04-02 05:25:36 |
| Message-ID: | alpine.DEB.2.21.2004020719140.16227@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
> FWIW, I don't think so. Generally a trailing backspace is an escape
> character for the following newline. And '\ ' is a escaped space,
> which is usualy menas a space itself.
>
> In this case escape character doesn't work generally and I think it is
> natural that a backslash in the middle of a line is a backslash
> character itself.
I concur: The backslash char is only a continuation as the very last
character of the line, before cr/nl line ending markers.
There are no assumption about backslash escaping, quotes and such, which
seems reasonable given the lexing structure of the files, i.e. records of
space-separated words, and # line comments.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-04-02 05:37:29 | Re: WAL usage calculation patch |
| Previous Message | Masahiko Sawada | 2020-04-02 05:25:18 | Re: Some problems of recovery conflict wait events |