Re: tuples too big

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: martin(dot)chantler(at)convergys(dot)com
Cc: mpm(at)norwottuck(dot)com, pgsql-general(at)postgresql(dot)org
Subject: Re: tuples too big
Date: 2001-02-08 15:41:45
Message-ID: 12062.981646905@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I've got a problem - I need a little help. I'm using 6.5.3 from Debian
> stable.
> I've got a database, which has some fields in one table that need to hold a
> fair bit of text (say, 8000-10,000+ characters). Right now, I've got those
> fields as simple text.

[ Martin suggests breaking up the large values by hand ]

Another answer is to update to 7.0.3, and redeclare your large fields as
'lztext'. This is a hack that is going away in 7.1 (it's superseded by
the more general TOAST feature), but it should buy you the extra couple
of K you need for now. A rough rule of thumb is that LZ compression
will save a factor of 2 or so on chunks of text.

A third possibility is to increase BLCKSZ from 8K to 32K, but that
requires a rebuild from source, so you might not want to mess with that
if you're accustomed to using RPMs.

These two answers are obviously hacks, so I'd agree with Martin's
approach if there were no better way on the horizon. But with 7.1
nearly out the door, I think it's silly to expend a lot of programming
effort to split up and reassemble records; the need for that will go
away as soon as you migrate to 7.1. What you want right now is a quick
and easy stopgap.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Raymond Chui 2001-02-08 15:49:48 How to ensure GMT time zone for Timestamp in PostgreSQL?
Previous Message Gunnar R|nning 2001-02-08 15:36:24 Re: full text searching