From: | Manfred Koizar <mkoi-pg(at)aon(dot)at> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Curt Sampson <cjs(at)cynic(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [PATCHES] Reduce heap tuple header size |
Date: | 2002-07-01 15:35:54 |
Message-ID: | 7vr0iu4ql04lsi8d04l4vegvv552s9o2t2@4ax.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Mon, 1 Jul 2002 10:15:42 -0400 (EDT), Bruce Momjian
<pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
>OK, I have heard enough votes to add this.
In a second version of this patch posted on 2002-06-26 you can control
the tuple format by #define/#undef PG72FORMAT. While there have been
voices saying that exposing this choice to the user via
configure --enable-pg72format
is not a good idea [well, it was one voice and the idea was called
"really, really bad" ;-) but the argument is still valid], I wonder
whether we shouldn't apply this second version (without the configure
parts) and put all forthcoming format changes under #ifndef
PG72FORMAT.
This way you can decide to go back to v7.2 format immediately before
going beta, if the changes are too hot to handle. And I think if I
wouldn't volunteer to cleanup the #ifdef PG72FORMAT stuff after the
new format has been accepted, I would be nominated to do it ...
Servus
Manfred
From | Date | Subject | |
---|---|---|---|
Next Message | Oleg Bartunov | 2002-07-01 15:52:11 | Re: Translated README.tree in tree.tar.gz |
Previous Message | Christopher Kings-Lynne | 2002-07-01 15:19:28 | Re: DROP COLUMN Proposal |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-07-01 17:10:01 | Re: [PATCHES] Reduce heap tuple header size |
Previous Message | Tom Lane | 2002-07-01 15:10:20 | Re: Wrap access to Oid in HeapTupleHeader |