| From: | Hannu Krosing <hannu(at)tm(dot)ee> |
|---|---|
| To: | The Hermit Hacker <scrappy(at)hub(dot)org> |
| 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-18 23:36:47 |
| Message-ID: | 3974EA0F.3EE8000B@tm.ee |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ...
-------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-18 23:47:49 | Re: btree split logic is fragile in the presence of large index items |
| Previous Message | Lamar Owen | 2000-07-18 23:03:26 | In the news... |