Hi,
As said, i am attaching the performance test results and the same patch
in this thread works with the latest CVS head.
Actually, i am seeing a slight performance improvement with the patch, which
i think might be either because of noise/ lesser pages. i ran it with the
default settings. i
I would work on this and try to present the performance test results.
I would also go ahead and examine, whether the logic can be added into
heap_form_tuple by any means.
Thanks,
Gokul.
On Wed, Mar 19, 2008 at 12:11 AM, Bruce Momjian [EMAIL PROTECTED] wrote:
Added to TODO:
* Consider
Added to TODO:
* Consider not storing a NULL bitmap on disk if all the NULLs are
trailing
http://archives.postgresql.org/pgsql-hackers/2007-12/msg00624.php
http://archives.postgresql.org/pgsql-patches/2007-12/msg00109.php
Tom's comments are:
We can also implement the same for index tuples.
On Dec 17, 2007 1:10 PM, Gokulakannan Somasundaram [EMAIL PROTECTED]
wrote:
Hi,
Currently we check for the existence of NULL values in the tuple and
we set the has_null flag. If the has_null flag is present, the tuple will be
storing
Gokulakannan Somasundaram [EMAIL PROTECTED] writes:
a) By modifying the functions, heap_form_tuple and heap_fill_tuple, we can
check whether all the nulls are trailing nulls. If all the nulls are
trailing nulls, then we will not set the has_null flag and we will not have
the null bitmap with
On Mon, 2007-12-17 at 13:10 +0530, Gokulakannan Somasundaram wrote:
Currently we check for the existence of NULL values in the tuple
and we set the has_null flag. If the has_null flag is present, the
tuple will be storing a null bitmap. What i propose is
Will this work for ALTER TABLE
On Dec 17, 2007 3:28 PM, Simon Riggs [EMAIL PROTECTED] wrote:
On Mon, 2007-12-17 at 13:10 +0530, Gokulakannan Somasundaram wrote:
Currently we check for the existence of NULL values in the tuple
and we set the has_null flag. If the has_null flag is present, the
tuple will be storing a
Thanks. I agree with you.
--
Thanks,
Gokul.
CertoSQL Project,
Allied Solution Group.
(www.alliedgroups.com)
Gregory Stark wrote:
Gokulakannan Somasundaram [EMAIL PROTECTED] writes:
a) By modifying the functions, heap_form_tuple and heap_fill_tuple, we can
check whether all the nulls are trailing nulls. If all the nulls are
trailing nulls, then we will not set the has_null flag and we will not
On Mon, 2007-12-17 at 08:47 -0500, Andrew Dunstan wrote:
This strikes me as such a corner case that it's likely not to be worth it.
If you really want to save space along these lines, one better place to
start might be mutable with column ordering - see
Hi,
Currently we check for the existence of NULL values in the tuple and we
set the has_null flag. If the has_null flag is present, the tuple will be
storing a null bitmap. What i propose is
a) By modifying the functions, heap_form_tuple and heap_fill_tuple, we can
check whether all the nulls
11 matches
Mail list logo
