From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Cindy <ctmoore(at)uci(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: question about upper limit on TEXT size |
Date: | 2002-08-13 20:47:39 |
Message-ID: | 996.1029271659@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Cindy <ctmoore(at)uci(dot)edu> writes:
> Tom Lane writes:
>>> Cindy <ctmoore(at)uci(dot)edu> writes:
>>>> 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:
Hmph --- that certainly shouldn't have any trouble with a measly 50K
text value. I wonder if you've somehow managed to turn off TOASTing
on this column? Could we see the output of
select * from pg_class where relname = 'searches';
and also the output of
select attname,attstorage from pg_attribute where attrelid =
(select oid from pg_class where relname = 'searches');
Do you see the same failure if you try to INSERT the data into
a freshly-created table, using the exact CREATE TABLE command you
just showed us?
> I could attach (or send separately) the exact INSERT command that generates
> the error message if you like.
If you want to send it to me (not the whole list), I'll be sure to try
it. I'll bet a nickel that it'll work for me though ... there's
something odd about this, and I'm not sure what.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-08-13 21:15:00 | Re: Read Lock For Foreign Key |
Previous Message | Hubert depesz Lubaczewski | 2002-08-13 20:31:09 | Re: when to use index, and when not to us index - *the* answer :) |