Skip site navigation (1) Skip section navigation (2)

Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Simon Riggs'" <simon(at)2ndQuadrant(dot)com>
Cc: "'Kevin Grittner'" <kgrittn(at)mail(dot)com>, <robertmhaas(at)gmail(dot)com>, <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: patch submission: truncate trailing nulls from heap rows to reduce the size of the null bitmap [Review]
Date: 2013-01-09 12:06:14
Message-ID: 00b301cdee61$b9994340$2ccbc9c0$@kapila@huawei.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wednesday, January 09, 2013 4:52 PM Simon Riggs wrote:
> On 24 December 2012 16:57, Amit Kapila <amit(dot)kapila(at)huawei(dot)com> wrote:
> 
> > Performance: Average of 3 runs of pgbench in tps
> > 9.3devel  |  with trailing null patch
> > ----------+--------------------------
> > 578.9872  |   573.4980
> 
> On balance, it would seem optimizing for this special case would
> affect everybody negatively; not much, but enough. Which means we
> should rekect this patch.
> 
> Do you have a reason why a different view might be taken?

I have tried to dig why this gap is coming. I have observed that there is
very less change in normal path.
I wanted to give it some more time to exactly find if something can be done
to avoid performance dip in normal execution.

Right now I am busy in certain other work. But definitely in coming week or
so, I shall spare time to work on it again.

With Regards,
Amit Kapila.



In response to

pgsql-hackers by date

Next:From: Amit KapilaDate: 2013-01-09 12:12:38
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Previous:From: Simon RiggsDate: 2013-01-09 11:59:00
Subject: Re: Further pg_upgrade analysis for many tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group