Let us know when you've added strlcpy () and we'll be happy to run some tests on the new code.
From: pgsql-hackers-owner(at)postgresql(dot)org on behalf of Tom Lane
Sent: Tue 9/26/2006 7:25 PM
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
pgsql-hackers by date
|Next:||From: Chris Mair||Date: 2006-09-27 13:07:28|
|Subject: Re: Please to technical check of upcoming release|
|Previous:||From: Simon Riggs||Date: 2006-09-27 11:30:43|
|Subject: Re: Cross-table statistics idea|
pgsql-patches by date
|Next:||From: Andrew Dunstan||Date: 2006-09-27 13:22:30|
|Subject: Re: Faster StrNCpy|
|Previous:||From: Claudio Natoli||Date: 2006-09-27 09:07:04|
|Subject: Re: Bad bug in fopen() wrapper code |