Re: Remove one use of IDENT_USERNAME_MAX - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Remove one use of IDENT_USERNAME_MAX
Date
Msg-id 062cc5e1-554e-7f5d-b7ea-1d9888679680@2ndquadrant.com
Whole thread Raw
In response to Re: Remove one use of IDENT_USERNAME_MAX  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2019-10-29 15:34, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes:
>> On 2019-10-28 14:45, Tom Lane wrote:
>>> Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
>>>> In think one of the reasons for the coding is the fact that *pw is
>>>> described to be placed in the static area, which can be overwritten by
>>>> succeeding calls to getpw*() functions.
> 
>>> Good point ... so maybe pstrdup instead of using a fixed-size buffer?
> 
>> Maybe.  Or we just decide that check_usermap() is not allowed to call
>> getpw*().  It's just a string-matching routine, so it doesn't have any
>> such business anyway.
> 
> I'm okay with that as long as you add a comment describing this
> assumption.

Committed with a pstrdup().  That seemed more consistent with other code 
in that file.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: pgbench - extend initialization phase control
Next
From: Peter Eisentraut
Date:
Subject: Re: Unix-domain socket support on Windows