From: | Chris Bitmead <chris(dot)bitmead(at)bigfoot(dot)com> |
---|---|
To: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] size limits on insert/copy/etc |
Date: | 1999-05-25 04:31:00 |
Message-ID: | 374A2784.923A028@bigfoot.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Unfortunately tuples cannot be bigger than 8k. Many of us I think look
forward to the day when this restriction doesn't apply (it is on the
to-do list), but at this point in time 8k is the limit.
Large objects will work, but they have other problems that make them
fairly impractical.
John Browning wrote:
>
> I'm trying to add large text items to a table (field declared as type
> text). PQSendQuery can't take more than 8192 bytes.That's OK. But COPY
> also complains that tuples of 29896 bytes are too big (trying to copy
> from a file). So how do I get big text fields into a table? Do I have to
> make them large objects? (And, if so, in what sense is the text field of
> "unlimited size"?) Or am I just missing something simple?
>
> Many thanks in advance for any advice...
>
> bests
>
> --
>
> John Browning // 71 Richmond Ave // London N1 0LX
> t 44 171 700 1230 // f 44 171 700 5255
From | Date | Subject | |
---|---|---|---|
Next Message | Gary Hoffman | 1999-05-25 05:57:32 | More pgsql compile problems on BSDi 3.0 |
Previous Message | John Browning | 1999-05-24 22:15:21 | size limits on insert/copy/etc |