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

From Amit Kapila
Subject Re: PG compilation error with Visual Studio 2015/2017/2019
Date
Msg-id CAA4eK1Ku41-gzt4NfL0EPyjpwU6__rqYv-rB2_APyXbT-mSQ4Q@mail.gmail.com
Whole thread Raw
In response to Re: PG compilation error with Visual Studio 2015/2017/2019  (Juan José Santamaría Flecha <juanjo.santamaria@gmail.com>)
Responses Re: PG compilation error with Visual Studio 2015/2017/2019
Re: PG compilation error with Visual Studio 2015/2017/2019
List pgsql-hackers
On Wed, May 6, 2020 at 4:19 AM Juan José Santamaría Flecha
<juanjo.santamaria@gmail.com> wrote:
>
> On Tue, May 5, 2020 at 1:34 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>>
>>
>> Apart from that, I have made a few other changes in comments, fixed
>> typos, and ran pgindent.  Let me know what do you think of attached
>> patches?
>
>
> The patches are definitely in better shape.
>
> 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.


--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: 邱宇航
Date:
Subject: Re: Optimization for hot standby XLOG_STANDBY_LOCK redo
Next
From: Fabien COELHO
Date:
Subject: Re: PG 13 release notes, first draft