Re: strncpy is not a safe version of strcpy - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: strncpy is not a safe version of strcpy
Date
Msg-id 20131115150412.GC17272@tamriel.snowman.net
Whole thread Raw
In response to Re: strncpy is not a safe version of strcpy  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: strncpy is not a safe version of strcpy  (Andres Freund <andres@2ndquadrant.com>)
List pgsql-hackers
* Andres Freund (andres@2ndquadrant.com) wrote:
> Sure, there can be longer paths, but postgres don't support them. In a
> *myriad* of places. It's just not worth spending code on it.
>
> Just about any of the places that use MAXPGPATH are "vulnerable" or
> produce confusing error messages if it's exceeded. And there are about
> zero complaints about it.

Confusing error messages are one thing, segfaulting is another.
Thanks,
    Stephen

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: strncpy is not a safe version of strcpy
Next
From: Andres Freund
Date:
Subject: Re: strncpy is not a safe version of strcpy