Received: from xxx-bfhxx-ms001.mowlem.com (mail2.mowlem.com [212.137.27.84]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f2UEomK55859 for ; Fri, 30 Mar 2001 09:50:48 -0500 (EST) (envelope-from Ben.Trewern@mowlem.com) Received: from xxx-bfhxx-ex002.mowlem.com (unverified) by xxx-bfhxx-ms001.mowlem.com (Content Technologies SMTPRS 4.2.1) with ESMTP id ; Sat, 31 Mar 2001 15:40:45 +0100 Received: by XXX_BFHXX_EX002 with Internet Mail Service (5.5.2650.21) id ; Fri, 30 Mar 2001 15:42:40 +0100 Message-ID: <996802F75C3CD411B424001083FA445B059561@CET_PONXX_FP001> From: "Trewern, Ben" To: "'Koen Antonissen'" , pgsql-sql@postgresql.org Subject: RE: Max Size of a text field Date: Fri, 30 Mar 2001 15:42:29 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative ; boundary="----_=_NextPart_001_01C0B927.ABC3BCAE" X-Archive-Number: 200103/643 X-Sequence-Number: 2322 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0B927.ABC3BCAE Content-Type: text/plain; charset="iso-8859-1" You can edit config.h and recompile 7.0.3 to allow for larger tuples (up to 32K - Info used to be in the FAQ but that has changed so try the mailing list archives for info) or you can try 7.1 RC1 or the CVS snapshot as both can deal with almost unlimited text fields ;-) Regards Ben > -----Original Message----- > From: Koen Antonissen [mailto:Koen@Cee-Kay.net] > Sent: 30 March 2001 12:52 > To: pgsql-sql@postgresql.org > Subject: [SQL] Max Size of a text field > > > Hi there > > I just recieved this error: > 'Warning: PostgreSQL query failed: ERROR: Tuple is too big: > size 13872, > max size 8140 ' > > Is there anyting I can do about that other than tell my users just not > typing so much text into the field? > > Kind regards, > Koen Antonissen > > ---------------------------(end of > broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > ***************************************************************************** This email and any attachments transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender and do not store, copy or disclose the content to any other person. It is the responsibility of the recipient to ensure that opening this message and/or any of its attachments will not adversely affect its systems. No responsibility is accepted by the Company. ***************************************************************************** ------_=_NextPart_001_01C0B927.ABC3BCAE Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: [SQL] Max Size of a text field

You can edit config.h and recompile 7.0.3 to allow for la= rger tuples (up to 32K - Info used to be in the FAQ but that has changed so= try the mailing list archives for info) or you can try 7.1 RC1 or the CVS = snapshot as both can deal with almost unlimited text fields ;-)

Regards

Ben

> -----Original Message-----
> From: Koen Antonissen [mailto:Koen@Cee-Kay.net]
> Sent: 30 March 2001 12:52
> To: pgsql-sql@postgresql.org
> Subject: [SQL] Max Size of a text field
>
>
> Hi there
>
> I just recieved this error:
> 'Warning: PostgreSQL query failed: ERROR: Tuple is = too big:
> size 13872,
> max size 8140 '
>
> Is there anyting I can do about that other than tel= l my users just not
> typing so much text into the field?
>
> Kind regards,
> Koen Antonissen
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please se= nd an appropriate
> subscribe-nomail command to majordomo@postgresql.or= g so that your
> message can get through to the mailing list cleanly=
>



***************************************************************************= **
This email and any attachments transmitted with it are confidential
and intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error please
notify the sender and do not store, copy or disclose the content
to any other person.

It is the responsibility of the recipient to ensure that opening this
message and/or any of its attachments will not adversely affect
its systems. No responsibility is accepted by the Company.
***************************************************************************= **
------_=_NextPart_001_01C0B927.ABC3BCAE--