Re: PG compilation error with Visual Studio 2015/2017/2019

From: davinder singh <davindersingh2692(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG compilation error with Visual Studio 2015/2017/2019
Date: 2020-05-07 04:24:51
Message-ID: CAHzhFSHAkgipjd_sT4L4+VOMr3Heb-gP0JrJ7=5NBumZpMqQVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 6, 2020 at 10:11 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:

>
> > 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.
>

I have verified/tested the latest patches for all versions and didn't find
any problem.
--
Regards,
Davinder
EnterpriseDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2020-05-07 04:47:40 Re: SLRU statistics
Previous Message vignesh C 2020-05-07 04:18:35 Re: Should smgrdounlink() be removed?