On 3 October 2016 at 22:55, Andres Freund <and...@anarazel.de> wrote: > A colleage of me just wrote innocent looking code like > char *shardRelationName = pnstrdup(relationName, NAMEDATALEN); > which is at the moment wrong if relationName isn't preallocated to > NAMEDATALEN size. [snip] > isn't that a somewhat weird behaviour / implementation? Not really like > strndup(), which one might believe to be analoguous...
Well I wouldn't say it's wrong, exactly. It might produce a segfault if relationName[NAMEDATALEN] is outside readable memory for the process, but otherwise it will behave as defined. Geoff -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers