Re: question about upper limit on TEXT size

Tom Lane writes:
>Cindy <ctmoore(at)uci(dot)edu> writes:
>> Hi, all. I'm working with a database record that includes one field
>> of type text. It's my understanding there is no upper limit on this
>> data type's size. However, I'm running into size related problems
>> with this. It could be due to the interface I'm using (my programs
>> are in C, and I'm using the libpq-fe.h interface (version 1.80 of
>> 2001/11/08). On the PGresult var I'm getting back, the
>> PQresultErrorMessage is telling me ERROR: Tuple is too big: size
>> 54776, max size 8128
>
><blink> What Postgres version are you using? If it's recent (7.1
>or later), could we see the full schema of your table?

7.2, on Solaris:

search_info=# CREATE TABLE searches (
search_info(# id SERIAL,
search_info(# uid VARCHAR(20),
search_info(# search_name VARCHAR(50),
search_info(# search_type INT,
search_info(# date_saved TIMESTAMP,
search_info(# date_lastupdated TIMESTAMP,
search_info(# parameters TEXT,
search_info(# temporary BOOLEAN
search_info(# );
<snip>
search_info=# \d searches
Table "searches"
Attribute | Type | Modifier

------------------+-------------+-----------------------------------------------
----
id | integer | not null default nextval('searches_id_seq'::te
xt)
uid | varchar(20) |
search_name | varchar(50) |
search_type | integer |
date_saved | timestamp |
date_lastupdated | timestamp |
parameters | text |
temporary | boolean |
Index: searches_id_key

I could attach (or send separately) the exact INSERT command that generates
the error message if you like. (I"m refraining from blasting a 54K file out
to the list, though :). It certainly doesn't seem to matter what's already
in the database, and I can successfully run the same INSERT command if I set
the parameters field to "" rather than its longer form.

Thanks,
--Cindy
--
ctmoore(at)uci(dot)edu