Received: from localhost (unknown [200.46.204.183])
	by mail.postgresql.org (Postfix) with ESMTP id 8E267632335;
	Wed, 21 Jan 2009 10:06:34 -0400 (AST)
Received: from mail.postgresql.org ([200.46.204.86])
	by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024)
	with ESMTP id 01489-06; Wed, 21 Jan 2009 10:06:26 -0400 (AST)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from is.rice.edu (is.rice.edu [128.42.42.24])
	by mail.postgresql.org (Postfix) with ESMTP id D882C632488;
	Wed, 21 Jan 2009 10:06:26 -0400 (AST)
Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160])
	by is.rice.edu (Postfix) with ESMTP id CD42941822;
	Wed, 21 Jan 2009 08:06:24 -0600 (CST)
Received: from is.rice.edu ([128.42.42.24])
	by scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160])
	(amavisd-new, port 10024)
	with ESMTP id 12591-03; Wed, 21 Jan 2009 08:06:23 -0600 (CST)
Received: by is.rice.edu (Postfix, from userid 18612)
	id 79A6C41819; Wed, 21 Jan 2009 08:06:23 -0600 (CST)
Date: Wed, 21 Jan 2009 08:06:23 -0600
From: Kenneth Marshall <ktm@rice.edu>
To: Grzegorz Ja??kiewicz <gryzman@gmail.com>
Cc: paulo matadr <saddoness@yahoo.com.br>, pgsql-general@postgresql.org,
	admin <pgsql-admin@postgresql.org>
Subject: Re: [GENERAL] bytea size limit?
Message-ID: <20090121140623.GG14570@it.is.rice.edu>
References: <359812.4771.qm@web52512.mail.re2.yahoo.com>
	<2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com>
User-Agent: Mutt/1.5.16 (2007-06-09)
X-Virus-Scanned: by amavis-2.2.1 at scan1.mail.rice.edu
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none
X-Spam-Level: 
X-Archive-Number: 200901/79
X-Sequence-Number: 31126

On Wed, Jan 21, 2009 at 01:55:28PM +0000, Grzegorz Ja??kiewicz wrote:
> there's no real limit (its size is described with 32bit number, and
> that's the only limitation here).
> But you need to be aware, that content is sent over at once, so memory
> is the limit in your case.
> 
> http://www.postgresql.org/docs/8.3/static/datatype-binary.html
> 
> For such large objects, it might be actually better to store them
> separate as files, and just store file name.
> 

The TOAST implementation however only allows 30-bits for the
size of the TOAST entry which caps the size at 2^30 or 1GB. I
agree that he could very well be limited also by the memory on
his system.

Cheers,
Ken