From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | schmid(at)ice(dot)mpg(dot)de, pgsql-general(at)postgresql(dot)org |
Subject: | Re: tuple too big error |
Date: | 2001-04-04 08:45:39 |
Message-ID: | Pine.LNX.4.21.0104041842370.4197-100000@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Richard,
On Wed, 4 Apr 2001, Richard Huxton wrote:
> >
> > 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.
>
> Afraid you have overlooked something - the 8k row limit applies to text
> fields too. You'll either need to use 7.1 (at release candidate stage) where
> this limit no longer applies, or large-objects.
Main problem with large objects with postgres 7.0 series (and before
this) is that ext2 does not scale well when number of hard links in a
given directory grows to anything like what I would expect a database with
DNA sequences in it would require.
I believe some directory splitting was planned for 7.1 release but I have
not seen this in the beta releases.
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | J.H.M. Dassen Ray | 2001-04-04 08:51:52 | Re: PostgreSQL and Rational Purify |
Previous Message | DaVinci | 2001-04-04 07:45:09 | unrecognized language plpgsql |