From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Ian Barwick <ian(dot)barwick(at)2ndquadrant(dot)com> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Sergei Kornilov <sk(at)zsrv(dot)org>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [PATCH] minor bugfix for pg_basebackup (9.6 ~ ) |
Date: | 2019-07-24 15:23:30 |
Message-ID: | 20190724152330.GA31403@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2019-Jul-24, Ian Barwick wrote:
> It'd be better if such a hypothetical option validated the provided
> slot name anwyay, to prevent later surprises.
Hmm, but what would we do if the validation failed?
> Revised patch attached, which as Alvaro suggests removes the escaping
> and adds a comment explaining why the raw value can be passed as-is.
Heh, yesterday I revised the original patch as attached and was about to
push when the bell rang. I like this one because it keeps the comment
to one line and it mentions the function name in charge of the
validation (useful for grepping later on). It's a bit laconic because
of the long function name and the desire to keep it to one line, but it
seems sufficient to me.
BTW upper case letters are not allowed :-)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
v3-0001-Don-t-uselessly-escape-a-string-that-doesn-t-need.patch | text/x-diff | 1.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2019-07-24 15:50:12 | Re: "localtime" value in TimeZone |
Previous Message | Shay Rojansky | 2019-07-24 15:19:40 | "localtime" value in TimeZone |