| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, btober(at)seaworthysys(dot)com, scrawford(at)pinpointresearch(dot)com, kleptog(at)svana(dot)org, m_tessier(at)sympatico(dot)ca, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: How many fields in a table are too many |
| Date: | 2003-06-28 17:43:32 |
| Message-ID: | 19148.1056822212@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Is this a TODO?
> When columns can be reordered, move varlena columns to the end?
Yeah, if it's not in there already. I remember seeing some Berkeley-era
comments speculating that this would be a good thing to do. Not sure if
they're still in the code, or
I believe that really what you want is fixed-width NOT NULL columns
first, then fixed-width nullable, then var-width. This ordering will
improve the odds of actually being able to use the fixed offset for
a particular column.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2003-06-28 17:58:13 | Re: How many fields in a table are too many |
| Previous Message | Bruce Momjian | 2003-06-28 17:38:26 | Re: How many fields in a table are too many |