| 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: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, 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 18:21:57 |
| Message-ID: | 23551.1056824517@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:
> Alvaro Herrera wrote:
>> This means that when you do ALTER TABLE ... SET/DROP NOT NULL the table
>> may have to be completely rewritten?
> I don't think we would change any physical ordering with ALTER TABLE ---
> just do it when the table is created, if possible.
Right, I was just thinking of this as an optimization we'd apply during
initial table creation. Renumbering columns later on would be a huge
mess, far more work than the optimization is worth.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2003-06-28 18:27:42 | Re: How many fields in a table are too many |
| Previous Message | Bruce Momjian | 2003-06-28 18:06:07 | Re: How many fields in a table are too many |