Re: TUPLE SIZE HELP

From: The Hermit Hacker <scrappy(at)hub(dot)org>
To: Hannu Krosing <hannu(at)tm(dot)ee>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Thomas Swan <tswan(at)olemiss(dot)edu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TUPLE SIZE HELP
Date: 2000-07-19 00:41:43
Message-ID: Pine.BSF.4.21.0007182141350.1745-100000@thelab.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 19 Jul 2000, Hannu Krosing wrote:

> The Hermit Hacker wrote:
> >
> > On Tue, 18 Jul 2000, Jan Wieck wrote:
> >
> > > Thomas Swan wrote:
> > > >
> > > > >That would be the wrong thing to change in any case. BLCKSZ in
> > > > >include/config.h is the value you can twiddle.
> > > >
> > > > Are there any plans to remove this limitation from the TEXT datatype? If
> > > > so, do you know what version we might see this in?
> > >
> > > It is already in the current development tree and will be
> > > shipped with the next release, scheduled for end of the year.
> >
> > Just a quick note ... with v7.x, you *can* use the lztext type to get by
> > the limitation ... its a temporary fix, but I believe that Vince is using
> > it for the web site for similar reasons to the original poster ...
>
> IIRC lztext does only compression and not splitting, so it just gets you
> so far ...

Correct ...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message The Hermit Hacker 2000-07-19 01:48:33 Re: [PORTS] Shared library search paths
Previous Message Mikheev, Vadim 2000-07-19 00:18:15 RE: btree split logic is fragile in the presence of lar ge index items