Re: be-secure-gssapi.c and auth.c with setenv() not compatible on Windows

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: be-secure-gssapi.c and auth.c with setenv() not compatible on Windows
Date: 2021-06-01 01:14:44
Message-ID: YLWKBB9TaHKVjPkf@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 31, 2021 at 09:14:36AM +0900, Michael Paquier wrote:
> I have been finally able to poke at that, resulting in the attached.
> You are right that adding only the fallback implementation for
> setenv() seems to be enough. I cannot get my environment to complain,
> and the code compiles.

Okay, applied this stuff to 12 and 13 to take care of the build
failures with hamerkop. The ECPG tests should also turn back to green
there.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2021-06-01 01:28:06 Re: CALL versus procedures with output-only arguments
Previous Message Tom Lane 2021-06-01 01:07:38 Re: Multiple hosts in connection string failed to failover in non-hot standby mode