This has been saved for the 8.2 release:
http://momjian.postgresql.org/cgi-bin/pgpatches_hold
---
Hiroki Kataoka wrote:
> Hi all,
>
> This small patch improves the performance of INSERT and UPDATE. By my
> machin
Tom Lane wrote:
I've been testing this patch a bit, and I'm unable to measure any
consistent improvement in pgbench times (sometimes it seems to win,
and some other times it doesn't). And gprof still swears up and down
that PageAddItem is only about 0.1% of the runtime, which would make
it impos
Tom Lane wrote:
> Hiroki Kataoka <[EMAIL PROTECTED]> writes:
>
This small patch improves the performance of INSERT and UPDATE. By my
machine, these changes raised the performance about 5%~10% in pgbench.
>>>
>>>BTW, in profiling the backend I've never seen PageAddItem take more than
>>>ab
Hiroki Kataoka <[EMAIL PROTECTED]> writes:
>>> This small patch improves the performance of INSERT and UPDATE. By my
>>> machine, these changes raised the performance about 5%~10% in pgbench.
>>
>> BTW, in profiling the backend I've never seen PageAddItem take more than
>> about 1% of the runtime
Tom Lane wrote:
This small patch improves the performance of INSERT and UPDATE. By my
machine, these changes raised the performance about 5%~10% in pgbench.
BTW, in profiling the backend I've never seen PageAddItem take more than
about 1% of the runtime, and in pgbench in particular it seems t
Tom Lane wrote:
> Hiroki Kataoka <[EMAIL PROTECTED]> writes:
>
>>This small patch improves the performance of INSERT and UPDATE. By my
>>machine, these changes raised the performance about 5%~10% in pgbench.
>
> Wouldn't it be a lot less invasive to search down from the end, instead
> of changin
Hiroki Kataoka <[EMAIL PROTECTED]> writes:
> This small patch improves the performance of INSERT and UPDATE. By my
> machine, these changes raised the performance about 5%~10% in pgbench.
BTW, in profiling the backend I've never seen PageAddItem take more than
about 1% of the runtime, and in pgbe
Hiroki Kataoka <[EMAIL PROTECTED]> writes:
> This small patch improves the performance of INSERT and UPDATE. By my
> machine, these changes raised the performance about 5%~10% in pgbench.
Wouldn't it be a lot less invasive to search down from the end, instead
of changing the page header format?
