MIME-Version: 1.0
References: <5EC17E17.7070002@anastigmatix.net>
 <5ECED046.3000308@anastigmatix.net>
 <CAASLQ4P11FFgefy_xK0Tcw3vWt1F1MNyVgK5eU=PFGvYrpZcyw@mail.gmail.com>
 <5ED0FCB0.405@anastigmatix.net> <5ED10C6D.2020000@anastigmatix.net>
 <5ED10F36.7060304@anastigmatix.net>
 <CAASLQ4PAQ0PNAxJ5ad9U6o+RT2ip19FXvgoK2y1kGWaJbTZ1WQ@mail.gmail.com>
 <5ED15825.9060504@anastigmatix.net>
 <CAASLQ4OXAb+_J=oK54PH5eYuXjkV9KMsoXEcp-TYaQPqxk1Xbg@mail.gmail.com>
 <5ED270BA.9010001@anastigmatix.net> <5ED3D488.1010401@anastigmatix.net>
 <5ED474CA.3000106@anastigmatix.net>
 <CAASLQ4PfvmgKPp+aFf_r5RsBwigc+EC5Hm2CuzwJSTDCT64i-A@mail.gmail.com>
 <5ED4EA10.4030801@anastigmatix.net>
 <CAASLQ4Px21jyb2vJYSrjF5P0RqhA-G_DDWR9QHG68r+W+AqbxQ@mail.gmail.com>
 <CAASLQ4NYE-TW6hjbkSOuAY2Z4NM2cYzqSQ9ahO2LAUhdP9axeQ@mail.gmail.com>
 <5ED7E74B.9020800@anastigmatix.net>
 <CAASLQ4Od6-0=3+4ENKh1Z-Wcu5Wir-bwUn_ccO2UCmDhoR4vtQ@mail.gmail.com>
 <5EDA576E.2000204@anastigmatix.net>
 <CAASLQ4OzPwZB6GG_cXNW4WU4zpHa6wm8Q3WRWNv5pZpis+gf3w@mail.gmail.com>
 <5EDBA5D9.8090506@anastigmatix.net>
In-Reply-To: <5EDBA5D9.8090506@anastigmatix.net>
From: Kartik Ohri <kartikohri13@gmail.com>
Date: Mon, 15 Jun 2020 22:17:09 +0530
Message-ID: 
 <CAASLQ4P8e9XfUh17HFhYE4eMtq5-C4dpHQAX+hCsia-UFNAjtA@mail.gmail.com>
Subject: Re: Starting build-system work (Windows/Mac users please speak up)
To: Chapman Flack <chap@anastigmatix.net>
Cc: pljava-dev@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000003a915f05a8222e74"
Precedence: bulk

--0000000000003a915f05a8222e74
Content-Type: text/plain; charset="UTF-8"

The pg_ctl stall issue has been fixed.

I am now trying to work around the Powershell streams. It seems psql writes
all its output including info, debug to error stream whereas Powershell has
a different stream for each of errors, warnings, debug and info. I have
been able to redirect all the output to stdout instead. However, this
redirects errors as well without failing the build. I am thinking of
manually processing the output to catch errors and manually terminate the
build in such a case. However, I think there might be a simpler solution to
use psql in quiet mode. What are your views on this ?

--0000000000003a915f05a8222e74
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The pg_ctl stall issue has been fixed.=C2=A0</div><di=
v><br></div><div>I am now trying to work around the Powershell streams. It =
seems psql writes all its output including info, debug to error stream wher=
eas Powershell has a different stream for each of errors, warnings, debug a=
nd info. I have been able to redirect all the output to stdout instead. How=
ever, this redirects errors as well without failing the build. I am thinkin=
g of manually processing the output to catch errors and manually terminate =
the build in such a case. However, I think there might be a simpler solutio=
n to use psql in quiet mode. What are your views on this ?</div></div>

--0000000000003a915f05a8222e74--