Re: [HACKERS] LONG

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Wieck <wieck(at)debis(dot)com>
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] LONG
Date: 1999-12-12 22:04:54
Message-ID: 199912122204.RAA09403@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Bruce Momjian wrote:
>
> > I disagree. By moving to another table, we don't have non-standard
> > tuples in the main table. We can create normal tuples in the long*
> > table, of identical format, and access them just like normal tuples.
> > Having special long tuples in the main table that don't follow the
> > format of the other tuples it a certain mess. The long* tables also
> > move the long data out of the main table so it is not accessed in
> > sequential scans. Why keep them in the main table?
>
> More ugly and complicated (especially for VACUUM) seems to
> me, the we need an index on these nonstandard tuples, that
> doesn't see the standard ones, while the regular indices
> ignore the new long tuples. At least if we want to delay
> reading of long values until they're explicitly requested.
>

Yes, good point. No reason to create non-standard tuples if you can
avoid it. And a separate table has performance advantages, especially
because the long tuples are by definition long and take up lots of
blocks.

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 1999-12-12 22:18:47 libpq questions...when threads collide
Previous Message Jan Wieck 1999-12-12 21:54:35 Re: [HACKERS] LONG