Re: Per tuple overhead, cmin, cmax, OID - Mailing list pgsql-hackers

From Manfred Koizar
Subject Re: Per tuple overhead, cmin, cmax, OID
Date
Msg-id cv8keug26puo9gil03hci8peesct2d6v4o@4ax.com
Whole thread Raw
In response to Re: Per tuple overhead, cmin, cmax  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Per tuple overhead, cmin, cmax, OID
List pgsql-hackers
On Thu, 02 May 2002 21:10:40 -0400, Tom Lane <tgl@sss.pgh.pa.us>
wrote:
>Manfred Koizar <mkoi-pg@aon.at> writes:
>> Is saving 4 bytes per tuple a "darn good reason"?
>
>[...] Now if
>we could get rid of 8 bytes in the header, I'd get excited ;-)

Tom,

what about WITHOUT OIDS?  I know dropping the OID from some tables and
keeping it for others is not trivial, because t_oid is the _first_
field of HeapTupleHeaderData.  I'm vaguely considering a few possible
implementations and will invest more work in a detailed proposal, if
it's wanted.

ServusManfred


pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: More schema queries
Next
From: Hannu Krosing
Date:
Subject: Re: Future plans