Re: Terrible performance on wide selects

From: "Dann Corbit" <DCorbit(at)connx(dot)com>
To: "Dann Corbit" <DCorbit(at)connx(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Steve Crawford" <scrawford(at)pinpointresearch(dot)com>, <pgsql-performance(at)postgreSQL(dot)org>, <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Terrible performance on wide selects
Date: 2003-01-23 00:22:51
Message-ID: D90A5A6C612A39408103E6ECDD77B8294CD864@voyager.corporate.connx.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

[snip]
> So (for instance) if you have 12 variable fields, you would
> store 12 integers at the start of the record.

Additionally, you could implicitly size the integers from the properties
of the column. A varchar(255) would only need an unsigned char to store
the offset, but a varchar(80000) would require an unsigned int.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message radha.manohar 2003-01-23 00:29:11 Re: Postgresql source
Previous Message Tom Lane 2003-01-23 00:21:24 Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2003-01-23 00:30:04 Re: Terrible performance on wide selects
Previous Message Tom Lane 2003-01-23 00:21:24 Re: [PERFORM] Proposal: relaxing link between explicit JOINs and execution order