Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Ryan Murphy <ryanfmurphy(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)
Date: 2016-08-18 20:11:27
Message-ID: CA+TgmobSSLBsUP7gFZw3cXAbePHwmrvh6gMvE3x+TY2ZSKNuXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 17, 2016 at 11:18 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On August 17, 2016 8:15:56 PM PDT, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>
>>+ { /* pg_ctl command w path, properly quoted */
>>+ PQExpBuffer pg_ctl_path = createPQExpBuffer();
>>+ printfPQExpBuffer(pg_ctl_path, "%s%spg_ctl",
>>+ bin_dir,
>>+ (strlen(bin_dir) > 0) ? DIR_SEP : ""
>>+ );
>>+ appendShellString(start_db_cmd, pg_ctl_path->data);
>>+ destroyPQExpBuffer(pg_ctl_path);
>>+ }
>>
>>This is not really project-style to have an independent block. Usually
>>those are controlled by for, while or if.
>
> Besides the comment positioning I'd not say that that is against the usual style, there's a number of such blocks already. Don't think it's necessarily needed here though...

Really? I'd remove such blocks before committing anything, or ask for
them to be removed, unless there were some special reason for having
them.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-08-18 20:15:25 Re: Patch: initdb: "'" for QUOTE_PATH (non-windows)
Previous Message Andres Freund 2016-08-18 20:10:51 Re: WIP: About CMake v2