Re: Per tuple overhead, cmin, cmax, OID
От
Manfred Koizar
Тема
Re: Per tuple overhead, cmin, cmax, OID
Дата
Msg-id
cv8keug26puo9gil03hci8peesct2d6v4o@4ax.com
Ответ на
Re: Per tuple overhead, cmin, cmax (Tom Lane)
Список
Дерево обсуждения
Per tuple overhead, cmin, cmax Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax, OID Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax, OID Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Manfred Koizar <mkoi-pg@aon.at>
Re: Per tuple overhead, cmin, cmax, OID Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID "Marc G. Fournier" <scrappy@hub.org>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID "Marc G. Fournier" <scrappy@hub.org>
Re: Per tuple overhead, cmin, cmax, OID Tom Lane <tgl@sss.pgh.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID "Marc G. Fournier" <scrappy@hub.org>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID "Marc G. Fournier" <scrappy@hub.org>
Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID) Tom Lane <tgl@sss.pgh.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, Bruce Momjian <pgman@candle.pha.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, "Marc G. Fournier" <scrappy@hub.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Karel Zak <zakkr@zf.jcu.cz>
Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID) Tom Lane <tgl@sss.pgh.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, "Marc G. Fournier" <scrappy@hub.org>
Re: Project scheduling issues (was Re: Per tuple overhead, cmin, cmax, OID) Tom Lane <tgl@sss.pgh.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, Bruce Momjian <pgman@candle.pha.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, "Marc G. Fournier" <scrappy@hub.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Lamar Owen <lamar.owen@wgcr.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Tom Lane <tgl@sss.pgh.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, Lamar Owen <lamar.owen@wgcr.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Jan Wieck <janwieck@yahoo.com>
Re: Project scheduling issues (was Re: Per tuple overhead, "Marc G. Fournier" <scrappy@hub.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Bruce Momjian <pgman@candle.pha.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, "Marc G. Fournier" <scrappy@hub.org>
Re: Project scheduling issues (was Re: Per tuple overhead, Bruce Momjian <pgman@candle.pha.pa.us>
Re: Project scheduling issues (was Re: Per tuple overhead, Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax, OID "Marc G. Fournier" <scrappy@hub.org>
Re: Per tuple overhead, cmin, cmax, OID Bruce Momjian <pgman@candle.pha.pa.us>
Re: Per tuple overhead, cmin, cmax Manfred Koizar <mkoi-pg@aon.at>
On Thu, 02 May 2002 21:10:40 -0400, Tom Lane wrote: >Manfred Koizar 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 по дате отправления