Re: Selecting a constant question

From: "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, "Dann Corbit" <DCorbit(at)connx(dot)com>
Cc: "Hannu Krosing" <hannu(at)skype(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Selecting a constant question
Date: 2007-06-12 10:47:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> Thats exactly the point. Consider
> select mytext from mytable ;
> How can PostgreSQL possibly know the maximum length of the
> returned values *before* it has scanned the whole table?

I think this focuses too much on those cases where it is not possible.
When it is not feasible like with a text column, clients deal with it
already (obviously some better than others).
It is for those cases where it would be feasible, like constants (or
concateneted columns), where the max length if properly returned could
be used to improve performance.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2007-06-12 11:01:10 Re: Selecting a constant question
Previous Message Magnus Hagander 2007-06-12 10:37:29 Re: Autovacuum launcher doesn't notice death of postmaster immediately