| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Peter Eisentraut <petere(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete) |
| Date: | 2007-02-11 06:27:17 |
| Message-ID: | 1015.1171175237@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2007-02-11 08:35:41 | Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete) |
| Previous Message | mark | 2007-02-11 05:31:21 | Re: [COMMITTERS] pgsql: StrNCpy -> strlcpy (not complete) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2007-02-11 06:36:16 | Re: Acclerating INSERT/UPDATE using UPS |
| Previous Message | Tom Lane | 2007-02-11 06:23:52 | Re: Acclerating INSERT/UPDATE using UPS |