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: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(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 11:22:06
Message-ID: CA+U5nMJgbpT67cft5FyCcyz2LUV5Zv+doo6yip7e8cs0r71X0g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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?

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2013-01-09 11:26:51
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Previous:From: Hannu KrosingDate: 2013-01-09 10:32:41
Subject: Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"

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