From: | wieck(at)debis(dot)com (Jan Wieck) |
---|---|
To: | hannu(at)tm(dot)ee (Hannu Krosing) |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgman(at)candle(dot)pha(dot)pa(dot)us, wieck(at)debis(dot)com, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] LONG |
Date: | 1999-12-11 23:05:37 |
Message-ID: | m11wva5-0003kGC@orion.SAPserv.Hamburg.dsh.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)debis(dot)com (Jan Wieck) #
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-12-11 23:25:12 | Re: [HACKERS] LONG |
Previous Message | Jan Wieck | 1999-12-11 22:36:22 | Re: [HACKERS] LONG |