From: | "Poul L(dot) Christiansen" <poulc(at)cs(dot)auc(dot)dk> |
---|---|
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 06:57:47 |
Message-ID: | Pine.GSO.4.21.0104040854540.10195-100000@borg.cs.auc.dk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
There is a max. tuple length of 8KB in PostgreSQL 7.0.3.
This limitation has been removed in ver. 7.1, which will be released soon.
My advise is too use PostgreSQL 7.1RC2, which is very stable, to get
around this problem.
Poul L. Christiansen
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.
>
> Thank you,
>
> Karl
>
> ----------------------------------------------------------------------
> Dr. Karl Schmid
> Max-Planck-Institute for Chemical Ecology
> Carl-Zeiss-Promenade 10 Tel: +49 3641 / 643658
> 07745 Jena Fax: +49 3641 / 643669
> Germany Email: schmid(at)ice(dot)mpg(dot)de
> ======================================================================
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://www.postgresql.org/search.mpl
>
From | Date | Subject | |
---|---|---|---|
Next Message | lec | 2001-04-04 07:04:59 | Can timeout duration be set? |
Previous Message | Karl Schmid | 2001-04-04 06:47:57 | tuple too big error |