Re: PG compilation error with Visual Studio 2015/2017/2019 - Mailing list pgsql-hackers

From Juan José Santamaría Flecha
Subject Re: PG compilation error with Visual Studio 2015/2017/2019
Date
Msg-id CAC+AXB0NtOqy7hLiVFh0MtMoyD-xRo9stRdRUZgqyhY1ai_N7A@mail.gmail.com
Whole thread Raw
In response to Re: PG compilation error with Visual Studio 2015/2017/2019  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: PG compilation error with Visual Studio 2015/2017/2019
List pgsql-hackers


On Wed, May 6, 2020 at 6:41 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
On Wed, May 6, 2020 at 4:19 AM Juan José Santamaría Flecha
>
> I think that the definition of get_iso_localename() should be consistent across all versions, that is HEAD like back-patched.
>

Fair enough.  I have changed such that get_iso_localename is the same
in HEAD as it is backbranch patches.  I have attached backbranch
patches for the ease of verification.
 
LGTM, and I see no regression in the manual SQL tests, so no further comments from my part.

Regards,

Juan José Santamaría Flecha

pgsql-hackers by date:

Previous
From: Victor Wagner
Date:
Subject: Re: Postgres Windows build system doesn't work with pythoninstalled in Program Files
Next
From: Jeremy Schneider
Date:
Subject: Re: SEQUENCE values (duplicated) in some corner cases when crashhappens