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

Re: Another idea for dealing with cmin/cmax

From: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: Another idea for dealing with cmin/cmax
Date: 2006-09-29 14:09:41
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Fri, Sep 29, 2006 at 01:15:06PM +0900, ITAGAKI Takahiro wrote:
> "Jim C. Nasby" <jim(at)nasby(dot)net> wrote:
> > The reason I thought of this is because once the transaction commits, we
> > have no use for the cid info. So we could do something like have
> > bgwriter look for tuples that belong to committed transactions before it
> > writes a page, and strip the cid out of them.
> Your concept is just like as the experimental method that I suggested before
> in
> We can remove cmin and cmax from commited tuples and xmin from frozen tuples
> and we might save some bytes in tuple headers.
> However, I think our next goal to shrink the headers is 16 bytes. The headers
> become 23 bytes using phantom cids and we are limited by alignments, so we will
> have no more advantages unless we delete extra 7 bytes in the headers.
> ...and it seems to be very difficult.

Dumb question... wouldn't getting down to 20 bytes buy us something?
Jim Nasby                                            jim(at)nasby(dot)net
EnterpriseDB      512.569.9461 (cell)

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2006-09-29 14:23:31
Subject: Re: Block B-Tree concept
Previous:From: Markus SchaberDate: 2006-09-29 14:03:50
Subject: Re: send()/receive() and on-disk storage

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