pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Barknecht <barknech@ph-cip.uni-koeln.de>
To: pgsql-sql@hub.org
Subject: Re: [SQL] Text type
Date: Thu, 14 Jan 1999 16:28:48 +0100
Message-ID: <19990114162848.A1573@fliwatut> (raw)
In-Reply-To: <F10BB1FAF801D111829B0060971D839F5DC74E@cpsmail>
References: <F10BB1FAF801D111829B0060971D839F5DC74E@cpsmail>

Jackson, DeJuan hat gesagt: // Jackson, DeJuan wrote:

> The current limit to a TEXT field is MAX_TUPLE_SIZE - TUPLE_OVERHEAD -
> ANY_OTHER_FIELD_SIZES_AND_OVERHEAD, which with no other fields in the
> table is just less than 8k.  But this can be increased at compile time.
> It's set to 8k because that tends to be optimal page size for most of
> the OS's that are supported.
> 	-DEJ

My question to this is: What to do if I need a big text field on a not
recompiled (8k buffer size) postgresql server?

I am developing a www backend with perl-DBI that keeps track of a lot of 
texts that can get longer than 8k. When inserting these they get cut off or
the query gives an error. 

I consider changing to a large object type field instead but how can I
conveniently insert, change and search the text there? 
(DBD::Pg does not have those nice lo_read() functions, just lo_import and 
lo_export) 

I think mine is a common problem. So I would be very happy if I could get 
some tips on how to handle large chunks of text with postgres (and perl)

Thank you,
-- 
                                                     __    __
 Frank Barknecht           ____ ______   ____ __ trip\ \  / /wire ______
                          / __// __  /__/ __// // __  \ \/ /  __ \\  ___\	
                         / /  / ____/  / /  / // ____// /\ \\  ___\\____ \	
                        /_/  /_____/  /_/  /_//_____// /  \ \\_____\\_____\
                                                    /_/    \_\ 



view thread (6+ messages)  latest in thread

Message-ID: <19990114162848.A1573@fliwatut>
Permalink:  ../19990114162848.A1573@fliwatut/
Also on:    postgresql.org/message-id/19990114162848.A1573@fliwatut

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: barknech@ph-cip.uni-koeln.de, pgsql-sql@hub.org
  Subject: Re: [SQL] Text type
  In-Reply-To: <19990114162848.A1573@fliwatut>
  References: <F10BB1FAF801D111829B0060971D839F5DC74E@cpsmail> <19990114162848.A1573@fliwatut>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox