Patch avoid call strlen repeatedly in loop.

2019-11-08 Thread Ranier VF
Hi, Please can anybody review and commit this patch. Thanks. Ranier Vilela --- \dll\postgresql-12.0\a\backend\libpq\auth.c Mon Sep 30 17:06:55 2019 +++ auth.c Fri Nov 08 14:27:17 2019 @@ -1815,6 +1815,7 @@ charident_user[IDENT_USERNAME_MAX + 1]; pgsocket

RE: Patch avoid call strlen repeatedly in loop.

2019-11-09 Thread Ranier VF
De: Mark Dilger Enviado: sábado, 9 de novembro de 2019 00:12 Para: Ranier VF; pgsql-hackers@lists.postgresql.org Assunto: Re: Patch avoid call strlen repeatedly in loop. On 11/8/19 9:41 AM, Ranier VF wrote: > --- \dll\postgresql-12.0\a\backend\li

RE: Patch avoid call strlen repeatedly in loop.

2019-11-09 Thread Ranier VF
er functions that make extensive use of strlen? Thank you. Ranier Vilela De: Mark Dilger Enviado: sábado, 9 de novembro de 2019 00:12 Para: Ranier VF; pgsql-hackers@lists.postgresql.org Assunto: Re: Patch avoid call strlen repeatedly in loop. On 11/8/19 9:

[PATH] spell.c (avoid call strlen repeatedly in loop.

2019-11-09 Thread Ranier VF
Hi Mark, Another example, can you take a look? --- \dll\postgresql-12.0\a\backend\tsearch\spell.c Mon Sep 30 17:06:55 2019 +++ spell.c Sat Nov 09 05:55:23 2019 @@ -186,7 +186,7 @@ #define MAX_NORM 1024 #define MAXNORMLEN 256 -#define STRNCMP(s,p) strncmp( (s), (p), strlen(p) )

[PATCH] Windows port: add support to setenv function

2019-12-18 Thread Ranier Vf
According to [1], windows does not support setenv. With the possibility of setenv going further [2], I am submitting in this thread, the patch to add setenv support on the windows side, It is based on pre-existing functions, and seeks to correctly emulate the functioning of the POSIX setenv, but

Re: Windows port minor fixes

2019-12-18 Thread Ranier Vf
Em qua., 18 de dez. de 2019 às 15:59, Stephen Frost escreveu: > >Alright, well, oddly enough, *this* email included the other headers and > >appears threaded properly (in mutt, at least). > > >Did you do something different when replying to this email vs. the other > >emails you've been replying

[PATCH] remove expression always false

2019-12-18 Thread Ranier Vf
Hi, || curpages <= 0 expression is always false and can be safely removed. Reasons: 1. curpages is uint32 type 2. its already test if is zero before. 3. Never be negative regards, Ranier Vilela diff --git a/src/backend/access/table/tableam.c b/src/backend/access/table/tableam.c index