Re: Faster StrNCpy

From: "Strong, David" <david(dot)strong(at)unisys(dot)com>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Faster StrNCpy
Date: 2006-09-27 13:02:46
Message-ID: B6419AF36AC8524082E1BC17DA2506E802579E0C@USMV-EXCH2.na.uis.unisys.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom,

Let us know when you've added strlcpy () and we'll be happy to run some tests on the new code.

David

________________________________

From: pgsql-hackers-owner(at)postgresql(dot)org on behalf of Tom Lane
Sent: Tue 9/26/2006 7:25 PM
To: josh(at)agliodbs(dot)com
Cc: pgsql-hackers(at)postgresql(dot)org; Neil Conway; Martijn van Oosterhout
Subject: Re: [HACKERS] Faster StrNCpy

Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> What I'd like to do immediately is put in strlcpy() and hit the two or
>> three places I think are performance-relevant.

> Immediately? Presumably you mean for 8.3?

No, I mean now. This is a performance bug and it's still open season on
bugs. If we were close to having a release-candidate version, I'd hold
off, but the above proposal seems sufficiently low-risk for the current
stage of the cycle.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chris Mair 2006-09-27 13:07:28 Re: Please to technical check of upcoming release
Previous Message Simon Riggs 2006-09-27 11:30:43 Re: Cross-table statistics idea

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2006-09-27 13:22:30 Re: Faster StrNCpy
Previous Message Claudio Natoli 2006-09-27 09:07:04 Re: Bad bug in fopen() wrapper code