From: | Einar Karttunen <ekarttun(at)cs(dot)Helsinki(dot)FI> |
---|---|
To: | Karl Schmid <schmid(at)ice(dot)mpg(dot)de> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: tuple too big error |
Date: | 2001-04-04 07:16:40 |
Message-ID: | Pine.LNX.4.30.0104041012030.1626-100000@tankar-11.cs.Helsinki.FI |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 4 Apr 2001, Karl Schmid wrote:
> Hi all,
>
> when I try to insert a long string (100 kByte) into a 'text' field using the
> following command:
>
> INSERT INTO clone (clone_code1, seq)
> VALUES ('TEL1N','CCCTAAACCCTAAA...<about 100,000 characters of DNA
> sequence>'),
>
> I get the following error message:
>
> ERROR: Tuple is too big: size 104228, max size 8140
>
> If I understand the docs correctly, there is no length restriction in text
> fields and the above instruction should work.
>
> Did I overlook something? Is it necessary to import such a long string as a
> large object?
>
> I am using PostgreSQL 7.0.3 under SuSE Linux 7.1.
>
PosrgreSQL 7.0.x has a compiletime tuplesize limit which is by default
8kb. This limitation doesn't exist in the 7.1 version, so I would suggest
getting it from ftp://ftp.postgresql.org/pub/dev/. It is still RC2, but
I think it can already be used in noncritical enviroments. Using large
objects is not a very good idea, because it is imho very cumbersome
in this case.
- Einar Karttunen
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Kreen | 2001-04-04 07:25:29 | Re: tuple too big error |
Previous Message | Einar Karttunen | 2001-04-04 07:11:21 | Re: Is this a bug in 7.0.2? |