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

From: Juan José Santamaría Flecha <juanjo(dot)santamaria(at)gmail(dot)com>
To: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, davinder singh <davindersingh2692(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-04-19 15:33:38
Message-ID: CAC+AXB2JN=cFokx+K_uNQP100viD7jpeHMSR2Sv7WG2H=TKOWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Apr 19, 2020 at 1:58 PM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> wrote:

> Em dom., 19 de abr. de 2020 às 07:16, Juan José Santamaría Flecha <
> juanjo(dot)santamaria(at)gmail(dot)com> escreveu:
>
>> On Sat, Apr 18, 2020 at 1:43 PM Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
>> wrote:
>>
>>> I have some observations about this patch, related to style, if you will
>>> allow me.
>>>
>> Please find attached a revised version.
>>
> Looks good to me, but, sorry, I think I missed a glitch in the previous
> review.
> If _create_locale fail, no need to call _free_locale(loct);.
>
> Another point is, what is the difference between pg_mbstrlen and wcslen?
> It would not be better to use only wcslen?
>

pg_mbstrlen() is for multibyte strings and wcslen() is for wide-character
strings, the "pg" equivalent would be pg_wchar_strlen().

Attached have the patch with this comments.
>

+ } else

This line needs a break, other than that LGTM.

Regards,

Juan José Santamaría Flecha

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Coleman 2020-04-19 16:14:39 Re: Incremental sorts and EXEC_FLAG_REWIND
Previous Message Ranier Vilela 2020-04-19 14:24:38 [PATCH] Small optimization across postgres (remove strlen duplicate usage)