Re: How many fields in a table are too many

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: 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-27 04:04:31
Message-ID: 24652.1056686671@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 the issue of many columns in a tuple the same issue as a SELECT
> having many columns?

I believe all the same inefficiencies need to be fixed whichever
way you look at it. Probably "many columns in SELECT" is the more
accurate description though.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Holger Marzen 2003-06-27 05:30:33 Solved: timestamp() broken in 7.2.4?
Previous Message Bruce Momjian 2003-06-27 03:12:55 Re: How many fields in a table are too many