From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Remove MSVC scripts from the tree |
Date: | 2023-11-20 07:00:09 |
Message-ID: | ecd3c0a5-8688-49bd-81d3-dc7a319a6431@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16.11.23 02:07, Andres Freund wrote:
> It doesn't seem like your patch has it quite that way? I see
>
> <sect2 id="installation-notes-mingw">
> <title>MinGW</title>
> ...
> <sect2 id="installation-notes-windows">
> <title>Windows</title>
>
> Where "Windows" actually seems to solely describe visual studio? That seems
> confusing.
I had suggested this arrangement as a way to reduce churn in this patch
set. We'd just move over the existing separate chapter into a new
section, and then later consider further rearrangements.
It's not always clear where all of these things should go, as there are
so many dimensions. For example, the existing sentence "After you have
everything installed, it is suggested that you run psql under CMD.EXE,
as the MSYS console has buffering issues.", does that apply to MinGW, or
really MSYS, or does it also apply if you build with Visual Something?
Ultimately, I don't think MinGW needs to be its own section.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Smith | 2023-11-20 07:01:42 | Simplify if/else logic of walsender CreateReplicationSlot |
Previous Message | jian he | 2023-11-20 06:57:37 | Re: SQL:2011 application time |