Horton

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

Simon Riggs <simon@2ndquadrant.com>

View thread View on postgr.es
From: Simon Riggs <simon@2ndQuadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Amit Kapila <amit.kapila@huawei.com>, Andres Freund <andres@2ndquadrant.com>, Craig Ringer <craig@2ndquadrant.com>, Jameison Martin <jameisonb@yahoo.com>, Noah Misch <noah@leadboat.com>, Kevin Grittner <kgrittn@mail.com>, Josh Berkus <josh@agliodbs.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2013-06-24T21:02:02Z
Lists: pgsql-hackers 
On 24 June 2013 21:50, Tom Lane <tgl@sss.pgh.pa.us> wrote:


> > So, Tom, how's that pluggable storage format coming?  :-)
>
> Well, actually, it's looking to me like heap_form_tuple will be
> underneath the API cut, because alternate storage managers will probably
> have other tuple storage formats --- column stores being the poster
> child here, but in any case the tuple header format is very unlikely
> to be universal.
>

Hopefully we would allow multiple storage managers to be active at once,
one per table?

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

Commits

  1. Don't assume that a tuple's header size is unchanged during toasting.