From: "Fujii Masao"
On Fri, Jan 24, 2014 at 9:00 PM, MauMau wrote:
OTOH, regarding PQhost(), I think we had better take my patch.
connectOptions2() computes and set derived values to PGconn, so that
PGconn's members have values which are actually used for connection. To
follow that rule, PGco
On Fri, Jan 24, 2014 at 9:00 PM, MauMau wrote:
> From: "Fujii Masao"
>
>> I think that 77035fa8a92d8c39f4c689e54f46813f203f09a8 fixed this problem.
>> Please check that.
>
>
> I looked through your patch. I'm fine with the PQhostaddr(). I didn't
> notice the problem when hostaddr was passed to
From: "Fujii Masao"
I think that 77035fa8a92d8c39f4c689e54f46813f203f09a8 fixed this problem.
Please check that.
I looked through your patch. I'm fine with the PQhostaddr(). I didn't
notice the problem when hostaddr was passed to psql on Windows.
OTOH, regarding PQhost(), I think we had b
On Wed, Dec 4, 2013 at 9:21 PM, MauMau wrote:
> Hello,
>
> I've found a bug that psql's \conninfo displays incorrect information on
> Windows. Please find attached the patch and commit this.
>
> [Problem]
> When I run "psql postgres" on Windows and execute \conninfo, it outputs the
> text below.
Hello,
I've found a bug that psql's \conninfo displays incorrect information on
Windows. Please find attached the patch and commit this.
[Problem]
When I run "psql postgres" on Windows and execute \conninfo, it outputs the
text below. It reports that psql connected to the server via UNIX do
