Re: Allow continuations in "pg_hba.conf" files - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: Allow continuations in "pg_hba.conf" files
Date
Msg-id 20200402.132543.416761724007436728.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: Allow continuations in "pg_hba.conf" files  (David Zhang <david.zhang@highgo.ca>)
Responses Re: Allow continuations in "pg_hba.conf" files  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
At Thu, 02 Apr 2020 00:20:12 +0000, David Zhang <david.zhang@highgo.ca> wrote in 
> Hi Fabien,
> Should we consider the case "\ ", i.e. one or more spaces after the backslash?
> For example, if I replace a user map 
> "mymap   /^(.*)@mydomain\.com$      \1" with 
> "mymap   /^(.*)@mydomain\.com$      \ "
> "\1"
> by adding one extra space after the backslash, then I got the pg_role="\\"
> but I think what we expect is pg_role="\\1"

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.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: Proposal: Expose oldest xmin as SQL function for monitoring
Next
From: Amit Kapila
Date:
Subject: User Interface for WAL usage data