Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Terrible performance on wide selects

From: Curt Sampson <cjs(at)cynic(dot)net>
To: Daniel Kalchev <daniel(at)digsys(dot)bg>
Cc: Hannu Krosing <hannu(at)tm(dot)ee>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Dann Corbit <DCorbit(at)connx(dot)com>,Steve Crawford <scrawford(at)pinpointresearch(dot)com>,pgsql-performance(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PERFORM] Terrible performance on wide selects
Date: 2003-01-23 15:50:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-performance
On Thu, 23 Jan 2003, Daniel Kalchev wrote:

> Does this mean, that constructing tables where fixed length fields are
> 'before' variable lenght fields and 'possibly null' fields might increase
> performance?

This, I believe, is why DB2 always puts (in physical storage) all of the
fixed-length fields before the variable-length fields.

Curt Sampson  <cjs(at)cynic(dot)net>   +81 90 7737 2974
    Don't you know, in this new Dark Age, we're all light.  --XTC

In response to

pgsql-performance by date

Next:From: Chantal AckermannDate: 2003-01-23 15:52:51
Subject: Re: [PERFORM] optimizing query
Previous:From: John LangeDate: 2003-01-23 15:36:11
Subject: Re: Query plan and Inheritance. Weird behavior

pgsql-hackers by date

Next:From: Ross J. ReedstromDate: 2003-01-23 17:26:54
Subject: Re: Call for objections: put back OIDs in CREATE TABLE AS/SELECT INTO
Previous:From: Curt SampsonDate: 2003-01-23 15:42:15
Subject: Re: Options for growth

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group