Re: [HACKERS] Savepoints... (row overhead)

From: Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at>
To: PostgreSQL Developers List <hackers(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] Savepoints... (row overhead)
Date: 1999-06-17 16:16:26
Message-ID: 219F68D65015D011A8E000006F8590C60267B3A0@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > If now we'll add 6 bytes to header then
> > offsetof(HeapTupleHeaderData, t_bits) will be 32 and for
> > no-nulls tuples there will be no difference at all
> > (with/without additional 6 bytes), due to double alignment
> > of header. So, the choice is: new feature or more compact
> > (than current) header for tuples with nulls.
>
> That's a tough one. What do other DB's have for row overhead?
>
Informix has a per page overhead of 36 bytes (per 4k or 2k page)
+ 4 bytes per row and page
Data resides on: Home page, big remainder page, remainder page.
no length or precision byte per column for fixed width/precision fields.
It has a maximum of 255 rows per page (4k page, 11 bytes min rowsize)

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 1999-06-17 16:21:02 Re: SOLVED: Re: [HACKERS] mirroring problem (www.postgresql.org)
Previous Message Ross J. Reedstrom 1999-06-17 16:14:55 Re: [HACKERS] Case tool