pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ansley, Michael <Michael.Ansley@intec.co.za>
Cc: 'stuart@comodo.net' <stuart@comodo.net>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] 8k limit
Date: Tue, 26 Oct 1999 12:16:49 -0400
Message-ID: <23186.940954609@sss.pgh.pa.us> (raw)
In-Reply-To: <1BF7C7482189D211B03F00805F8527F748C1BC@S-NATH-EXCH2>

"Ansley, Michael" <Michael.Ansley@intec.co.za> writes:
> The 8kB limit you are refering to is probably the tuple-length limit.  This
> can be altered to a maximum of 64kB (I think, might only be 32kB),

32k; otherwise Michael's comments are accurate.

>>> been discussed here before =). Next question is whats the 
>>> max number of large
>>> objects you can store? I think its about 4 billion , am i wrong?

Each LO results in the creation of two files in your database directory,
which means performance will get pretty horrible when you get past a
few thousand LOs (at least on most flavors of Unix, which are not
optimized for huge directories).

There has been discussion of fixing this, eg by making a subdirectory
tree for LOs, but I'd rather see us put our effort into eliminating
the tuple length limit.

			regards, tom lane



view thread (6+ messages)  latest in thread

Message-ID: <23186.940954609@sss.pgh.pa.us>
Permalink:  ../23186.940954609@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/23186.940954609@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Michael.Ansley@intec.co.za, stuart@comodo.net
  Subject: Re: [INTERFACES] 8k limit
  In-Reply-To: <23186.940954609@sss.pgh.pa.us>

* 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