Postgres Pro
Downloads
Home   >   mailing lists

Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete)
Date
Msg-id 1015.1171175237@sss.pgh.pa.us
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete)  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Tree view 
Bruce Momjian <bruce@momjian.us> writes:
> Woh.  Peter, you realize one of the reasons we use StrNCpy as a macro is
> for performance.  I don't see strlcpy as a macro.

Huh?  StrNCpy is a wrapper around strncpy().  Do you have reason to
think that strncpy() is especially tightly implemented on most
platforms?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Acclerating INSERT/UPDATE using UPS
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Acclerating INSERT/UPDATE using UPS