Re: psql's EDITOR behavior on Windows - Mailing list pgsql-hackers

From Pavlo Golub
Subject Re: psql's EDITOR behavior on Windows
Date
Msg-id CAK7ymcLsdnYY9ExSf24U9CU0OQ+G7PnbadLb8EMdTKRqn2n67A@mail.gmail.com
Whole thread Raw
In response to Re: psql's EDITOR behavior on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Wed, Dec 18, 2019 at 4:11 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> I wrote:
> > Pavlo Golub <pavlo.golub@cybertec.at> writes:
> >> I cannot find the reason why EDITOR value on Windows is quoted.
>
> > The comment you quoted explains it: apparently people expect
> > paths-with-spaces to work in that value without any manual quoting.
>
> Actually, after digging in the git history and archives, the current
> behavior seems to trace back to a discussion on pgsql-hackers on
> 2004-11-15.  The thread linkage in the archives seems rather incomplete,
> but it boiled down to this:
>
> https://www.postgresql.org/message-id/9045.1100539151%40sss.pgh.pa.us
>
> ie, the argument that people could handle space-containing paths by
> putting double quotes into the environment variable's value is just wrong.
> Possibly Microsoft fixed that in the fifteen years since, but I'd want to
> see some proof.

Interesting. Thanks. I'll prepare a patch showing the case.

>
>                         regards, tom lane



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Read Uncommitted
Next
From: Stephen Frost
Date:
Subject: Re: Allow cluster owner to bypass authentication