Yes, I assume that the patch to group the writes isn't something we want
right now, and the one for O_DIRECT is going to need an additional
fsync, and I have asked for testing on that.
I have posted a patch that I think fixes the memory leak reported and am
waiting for feedback on that.
On Tue, 2005-03-01 at 13:53 -0800, Mark Wong wrote:
> On Thu, Feb 03, 2005 at 07:25:55PM +0900, ITAGAKI Takahiro wrote:
> > Hello everyone.
> >
> > I fixed two bugs in the patch that I sent before.
> > Check and test new one, please.
>
> Ok, finally got back into the office and was able to run 1
On Thu, Feb 03, 2005 at 07:25:55PM +0900, ITAGAKI Takahiro wrote:
> Hello everyone.
>
> I fixed two bugs in the patch that I sent before.
> Check and test new one, please.
Ok, finally got back into the office and was able to run 1 set of
tests.
So the new baseline result with 8.0.1:
http
This has been saved for the 8.1 release:
http://momjian.postgresql.org/cgi-bin/pgpatches2
---
ITAGAKI Takahiro wrote:
> Hello everyone.
>
> I fixed two bugs in the patch that I sent before.
> Check and test new one
Hello everyone.
I fixed two bugs in the patch that I sent before.
Check and test new one, please.
1. Fix update timing of Write->curridx. (pointed by Tom)
Change to update it soon after write().
2. Fix buffer alignment routine on 64bit cpu. (pointed by Mark)
I checked it on Xeon EM64T
Hmm... I don't remember specifying a datatype. I suppose whatever the
default one is. :)
I'll be happy to test again, just let me know.
Mark
On Fri, Jan 28, 2005 at 06:28:32AM +0900, ITAGAKI Takahiro wrote:
> Thanks for testing, Mark!
>
> > I gave this a try with DBT-2, but got a core dump on
Thanks for testing, Mark!
> I gave this a try with DBT-2, but got a core dump on our ia64 system.
> I hope this isn't a random thing, like I ran into previously. Maybe
> I'll try again, but postgres dumped core.
Sorry, this seems to be my patch's bug.
Which datatype did you compile with? LP64, I
