Re: [HACKERS] LONG - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] LONG
Date
Msg-id m11wva5-0003kGC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Re: [HACKERS] LONG  (Hannu Krosing <hannu@tm.ee>)
Responses Re: [HACKERS] LONG
List pgsql-hackers
Hannu Krosing wrote:

> Tom Lane wrote:
> >
> >
> > But I don't really see why this would be either easier to do or
> > more reliable than storing multiple segments of a tuple in the
> > primary relation itself.  And I don't much care for
> > institutionalizing a hack like a special "LONG" datatype.
>
> AFAIK the "hack" is similar to what Oracle does.
>
> At least this is my impression from some descriptions, and it also
> seems reasonable thing to do in general as we dont want to read in
> 500K tuples (and then sort them) just to join on int fields and filter
> out on boolean and count(n) < 3.

    Even  if  this  is  a  side  effect  I  haven't  seen  at the
    beginning, it would be one of the  best  side  effect's  I've
    ever  seen.  A  really  tempting  one  that's worth to try it
    anyway.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] LONG
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] LONG