I everyone, need help!!!
My aplication return erro:
2009-01-20 10:22:03,264 INFO [STDOUT] Caused by: org.postgresql.= util.

PSQLException: ERROR: inv= alid memory alloc request size 1705447581

TABLE batch.re= latorio_gerado

rege_id integer NOT NULL,
fuin_id i= nteger NOT NULL,
rela_id integer NOT NULL,
rege_tmultim= aalteracao timestamp without time zone NOT NULL DEFAULT now(),
re= ge_nnpaginas integer NOT NULL,
rege_binario bytea,
rege_pdf bytea

I get this erro above refers the col= umn "rege_pdf bytea" , when try generate report in pdf.

thanks for help <= br>

=0A=0A=0A

Veja quais s=C3=A3o os assuntos do mome= nto no Yahoo! + Buscados: Top 10 - Celebridades - M=C3=BAsica - Esportes --0-140334809-1232544063=:4771-- From ktm@rice.edu Wed Jan 21 13:54:53 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 7B2A16323CA; Wed, 21 Jan 2009 09:54:53 -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 88167-03; Wed, 21 Jan 2009 09:54:49 -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 437FB6323BE; Wed, 21 Jan 2009 09:54:50 -0400 (AST) Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) by is.rice.edu (Postfix) with ESMTP id A70A641820; Wed, 21 Jan 2009 07:54:47 -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 08900-10; Wed, 21 Jan 2009 07:54:46 -0600 (CST) Received: by is.rice.edu (Postfix, from userid 18612) id 5077941819; Wed, 21 Jan 2009 07:54:46 -0600 (CST) Date: Wed, 21 Jan 2009 07:54:45 -0600 From: Kenneth Marshall To: paulo matadr Cc: pgsql-general@postgresql.org, admin Subject: Re: bytea size limit? Message-ID: <20090121135445.GF14570@it.is.rice.edu> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <359812.4771.qm@web52512.mail.re2.yahoo.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/77 X-Sequence-Number: 31124 On Wed, Jan 21, 2009 at 05:21:03AM -0800, paulo matadr wrote: > I everyone, need help!!! > My aplication return erro: > > 2009-01-20 10:22:03,264 INFO [STDOUT] Caused by: org.postgresql.util. > PSQLException: ERROR: invalid memory alloc request size 1705447581 > > TABLE batch.relatorio_gerado > > rege_id integer NOT NULL, > fuin_id integer NOT NULL, > rela_id integer NOT NULL, > rege_tmultimaalteracao timestamp without time zone NOT NULL DEFAULT now(), > rege_nnpaginas integer NOT NULL, > rege_binario bytea, > rege_pdf bytea > > I get this erro above refers the column "rege_pdf bytea" , when try generate report in pdf. > > thanks for help > I believe that the default size limit for a bytea or text field is currently 1GB. Ken From gryzman@gmail.com Wed Jan 21 14:01:29 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id F34AB63255A; Wed, 21 Jan 2009 10:01:29 -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 95571-08; Wed, 21 Jan 2009 10:01:20 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f13.google.com (mail-bw0-f13.google.com [209.85.218.13]) by mail.postgresql.org (Postfix) with ESMTP id 706506323CA; Wed, 21 Jan 2009 09:59:57 -0400 (AST) Received: by bwz6 with SMTP id 6so607001bwz.19 for ; Wed, 21 Jan 2009 05:59:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=lFmvLCcvziR8PNdOzmKBTSA9wdUyqc5xBa0Bv/Tm6OM=; b=KEiUmLuv2arBgZ5dNGRSYSIO8pSaOYZBYbaSz0bgly2vZjnzxQ3gD2kmTX7y3HHVYL v0H81nXPijwcYDIazwJqXwQuKj6Oe4swQSvsuv2BmUJS8sK21tHB1VDV3LoQp9onbwfa +kSPCyCN30siHztEbJTQDt9CAtLQWiZui/t8w= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=NG/a9Ok9Kii7jUVNWjVrljRCpo1NsnRcFVcWR/CBv8D+sFeg6yxHtxeXCuJV2mDgIh nDzKO7J6890bFboJaQgo5j6v2mFVTcQ9bp4EKKRck1BEEbRrJKSvSgftHh+V/PArPIyj ulSeqfCiq4tczQLryEJzR5f0M35pnuAKYahRI= MIME-Version: 1.0 Received: by 10.181.226.2 with SMTP id d2mr2909901bkr.15.1232546128346; Wed, 21 Jan 2009 05:55:28 -0800 (PST) In-Reply-To: <359812.4771.qm@web52512.mail.re2.yahoo.com> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> Date: Wed, 21 Jan 2009 13:55:28 +0000 Message-ID: <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> Subject: Re: [GENERAL] bytea size limit? From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= To: paulo matadr Cc: pgsql-general@postgresql.org, admin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/78 X-Sequence-Number: 31125 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. From ktm@rice.edu Wed Jan 21 14:06:34 2009 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 To: Grzegorz Ja??kiewicz Cc: paulo matadr , pgsql-general@postgresql.org, admin 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 From gryzman@gmail.com Wed Jan 21 14:12:40 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id AAB3E6323BE; Wed, 21 Jan 2009 10:12:40 -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 09515-01; Wed, 21 Jan 2009 10:12:36 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f13.google.com (mail-bw0-f13.google.com [209.85.218.13]) by mail.postgresql.org (Postfix) with ESMTP id F0B5F632335; Wed, 21 Jan 2009 10:12:35 -0400 (AST) Received: by bwz6 with SMTP id 6so619015bwz.19 for ; Wed, 21 Jan 2009 06:12:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=3tjWaY83VFKxESVP1MVxPaemqqeTIj0YErQaNxKqhQU=; b=aSnlAWbyZwfpHzlIgDyjY45bM3hHv11Bju4MrxXYzP/Wp0V8IByjrpa/6V2Y1q9fdd aTL+za54z6QjVbNnciY/9bNoLbFF/F2n+exj9X7Ciz8lAH2NqBKZM2Q8IIuPAbaHMdEV Zx/Ft/ZQ6pH6iqOaA5o+92DNbEl0W98LGvMZo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uZr/lX8Csa2cmdwLZk9e+Dk32Tz/RasXMNFbYpQ558OW4PbIUt7nT6UP2fk5H/gzGK 2Z3N5ZpkpGHndF9JFg0auJkhxSySNnRBJj91tAl+xdnpVh6nFQj2dpNvKAUGsadIBvpA C0oaLEzw/lrjMQGwupc+ELSmGdCCABpMX+hds= MIME-Version: 1.0 Received: by 10.180.213.15 with SMTP id l15mr2905063bkg.115.1232546941469; Wed, 21 Jan 2009 06:09:01 -0800 (PST) In-Reply-To: <20090121140623.GG14570@it.is.rice.edu> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> <20090121140623.GG14570@it.is.rice.edu> Date: Wed, 21 Jan 2009 14:09:01 +0000 Message-ID: <2f4958ff0901210609j7ead1ca6k7b170f3e2be21448@mail.gmail.com> Subject: Re: [GENERAL] bytea size limit? From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= To: Kenneth Marshall Cc: paulo matadr , pgsql-general@postgresql.org, admin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/80 X-Sequence-Number: 31127 On Wed, Jan 21, 2009 at 2:06 PM, Kenneth Marshall wrote: > 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. i wasn't aware of that, and also - it doesn't say anything about it in docs. As for limitations, that also depends on db drivers he is using, etc, etc. I use bytea to store 100-200MB objects in many dbs, but I wouldn't go as far as 1.5GB ... -- GJ From ktm@rice.edu Wed Jan 21 14:18:01 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 2C357632495; Wed, 21 Jan 2009 10:18:01 -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 12990-10; Wed, 21 Jan 2009 10:17:54 -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 E2551632480; Wed, 21 Jan 2009 10:17:54 -0400 (AST) Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) by is.rice.edu (Postfix) with ESMTP id 820EC41822; Wed, 21 Jan 2009 08:17:49 -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 11790-07; Wed, 21 Jan 2009 08:17:48 -0600 (CST) Received: by is.rice.edu (Postfix, from userid 18612) id BCF5641819; Wed, 21 Jan 2009 08:17:48 -0600 (CST) Date: Wed, 21 Jan 2009 08:17:48 -0600 From: Kenneth Marshall To: Grzegorz Ja??kiewicz Cc: paulo matadr , pgsql-general@postgresql.org, admin Subject: Re: [GENERAL] bytea size limit? Message-ID: <20090121141748.GH14570@it.is.rice.edu> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> <20090121140623.GG14570@it.is.rice.edu> <2f4958ff0901210609j7ead1ca6k7b170f3e2be21448@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2f4958ff0901210609j7ead1ca6k7b170f3e2be21448@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/81 X-Sequence-Number: 31128 On Wed, Jan 21, 2009 at 02:09:01PM +0000, Grzegorz Ja??kiewicz wrote: > On Wed, Jan 21, 2009 at 2:06 PM, Kenneth Marshall wrote: > > > 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. > > i wasn't aware of that, and also - it doesn't say anything about it in docs. > As for limitations, that also depends on db drivers he is using, etc, > etc. I use bytea to store 100-200MB objects in many dbs, but I > wouldn't go as far as 1.5GB ... > The reference is in: http://www.postgresql.org/docs/8.3/static/storage-toast.html Here is the pertinent excerpt: Only certain data types support TOAST -- there is no need to impose the overhead on data types that cannot produce large field values. To support TOAST, a data type must have a variable-length (varlena) representation, in which the first 32-bit word of any stored value contains the total length of the value in bytes (including itself). TOAST does not constrain the rest of the representation. All the C-level functions supporting a TOAST-able data type must be careful to handle TOASTed input values. (This is normally done by invoking PG_DETOAST_DATUM before doing anything with an input value, but in some cases more efficient approaches are possible.) TOAST usurps two bits of the varlena length word (the high-order bits on big-endian machines, the low-order bits on little-endian machines), thereby limiting the logical size of any value of a TOAST-able data type to 1 GB (230 - 1 bytes). When both bits are zero, the value is an ordinary un-TOASTed value of the data type, and the remaining bits of the length word give the total datum size (including length word) in bytes. When the highest-order or lowest-order bit is set, the value has only a single-byte header instead of the normal four-byte header, and the remaining bits give the total datum size (including length byte) in bytes. As a special case, if the remaining bits are all zero (which would be impossible for a self-inclusive length), the value is a pointer to out-of-line data stored in a separate TOAST table. (The size of a TOAST pointer is given in the second byte of the datum.) Values with single-byte headers aren't aligned on any particular boundary, either. Lastly, when the highest-order or lowest-order bit is clear but the adjacent bit is set, the content of the datum has been compressed and must be decompressed before use. In this case the remaining bits of the length word give the total size of the compressed datum, not the original data. Note that compression is also possible for out-of-line data but the varlena header does not tell whether it has occurred -- the content of the TOAST pointer tells that, instead. Cheers, Ken From gryzman@gmail.com Wed Jan 21 14:26:20 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C8A00632480; Wed, 21 Jan 2009 10:26:20 -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 22979-10; Wed, 21 Jan 2009 10:26:14 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f13.google.com (mail-bw0-f13.google.com [209.85.218.13]) by mail.postgresql.org (Postfix) with ESMTP id C521063249C; Wed, 21 Jan 2009 10:26:10 -0400 (AST) Received: by bwz6 with SMTP id 6so632976bwz.19 for ; Wed, 21 Jan 2009 06:26:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=LrtSotTUiwun1Rf8EITYUMi8Gi3+AcRH3EYGYG2HTQQ=; b=BGhoTTIBgxqcwy6krhgfyn6BeqZfMmjUCCd9aXOio7qxEI/bqc2NR513ZcBa29qiUb lHuXPidgG2czuqFubIURLghqRIJJYXtrBChUtRlxo9Dl64Hm6bEm+uxh0bRzmtetLHLi 5u3Ywe7cCR38HpJ7PhRbVC1biMaPVUr1dXhIc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=F2wjeQxz0Y4+D1xJo8awuB+0X+BCdmQYQkaLNSrmeWJRkCTAdXfUt2GYVqPCNCaqRT P7reFDiL0nnXIXC7ijE0QKO1QPQXCSTKD1tr9EmOVRGaBxPk9OFMJPdbA3CBB0XK3Y+Y Wh6K57Xqub7abnA9rh7o6GXFZyz+CEStfj1sQ= MIME-Version: 1.0 Received: by 10.180.205.1 with SMTP id c1mr432862bkg.143.1232547741629; Wed, 21 Jan 2009 06:22:21 -0800 (PST) In-Reply-To: <20090121141748.GH14570@it.is.rice.edu> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> <20090121140623.GG14570@it.is.rice.edu> <2f4958ff0901210609j7ead1ca6k7b170f3e2be21448@mail.gmail.com> <20090121141748.GH14570@it.is.rice.edu> Date: Wed, 21 Jan 2009 14:22:21 +0000 Message-ID: <2f4958ff0901210622p37e28421lc0f1abc224fa4bc4@mail.gmail.com> Subject: Re: [GENERAL] bytea size limit? From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= To: Kenneth Marshall Cc: paulo matadr , pgsql-general@postgresql.org, admin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/83 X-Sequence-Number: 31130 you don't have to quote everything :) I ment, there's nothing on bytea on its doc page, where one would expect to read it. From gryzman@gmail.com Wed Jan 21 15:09:21 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 68F98632417; Wed, 21 Jan 2009 11:09:21 -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 70871-08; Wed, 21 Jan 2009 11:09:17 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f16.google.com (mail-bw0-f16.google.com [209.85.218.16]) by mail.postgresql.org (Postfix) with ESMTP id B39486323BE; Wed, 21 Jan 2009 11:09:15 -0400 (AST) Received: by bwz9 with SMTP id 9so880bwz.19 for ; Wed, 21 Jan 2009 07:09:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=E5M4NFmquLIE1gUNMclpJtdMfYG7LVE+eQnjnOi1okk=; b=aNGgctnz3qugmASvGZvP1oYtllPGJ/RepYEYDvf/hKwZBO94dUly1fgnJrAPfT2IHO 5SFCDYLx7fAEiTvhiDjSJKVBWRIRGEaAhcbajRnJImPgzNssqul8HEeTUKDxQSOeaQjF hBVsOe492skWmcDFi700pvuD9gnVh3jCpgqJg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=GtL4EFl27AuNap8nS02lt/gTTTuJRyID78GUAWjdVSB0STNuvKY4KsGmB6qhm72J2U T8davrrsR020XkI0poSO0sl0jJ2LGSFM0cDkxefredUfy78rrCxGx1dP3ZE3lUF4Ukej 3RETWWoVeGRAfl6BB3PAENeLbnRV8ccR7pn0E= MIME-Version: 1.0 Received: by 10.181.138.13 with SMTP id q13mr2925988bkn.95.1232550433359; Wed, 21 Jan 2009 07:07:13 -0800 (PST) In-Reply-To: <901365.77018.qm@web52506.mail.re2.yahoo.com> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> <20090121140623.GG14570@it.is.rice.edu> <901365.77018.qm@web52506.mail.re2.yahoo.com> Date: Wed, 21 Jan 2009 15:07:13 +0000 Message-ID: <2f4958ff0901210707v5e639b39of59f678a19981c30@mail.gmail.com> Subject: Re: [GENERAL] bytea size limit? From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= To: paulo matadr Cc: Kenneth Marshall , pgsql-general@postgresql.org, admin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/88 X-Sequence-Number: 31135 On Wed, Jan 21, 2009 at 3:02 PM, paulo matadr wrote: > My system have very large ram size, so its possible review postgresql.conf ? > all depends on how you access DB, what type of drivers (odbc, libpq, etc, etc). See, every time you pass a row , they usually have to allocate that much memory, not only its quite inefficient, but also slow. As for the configuration option, I am interested in knowing myself too :) -- GJ From ktm@rice.edu Wed Jan 21 15:14:02 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id D400C632520; Wed, 21 Jan 2009 11:14:02 -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 79076-02-2; Wed, 21 Jan 2009 11:13:59 -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 D4FAD632525; Wed, 21 Jan 2009 11:13:59 -0400 (AST) Received: from scan1.mail.rice.edu (scan1.mail.rice.edu [128.42.58.160]) by is.rice.edu (Postfix) with ESMTP id 70E6541820; Wed, 21 Jan 2009 09:13:57 -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 13278-04; Wed, 21 Jan 2009 09:13:56 -0600 (CST) Received: by is.rice.edu (Postfix, from userid 18612) id AFF6241819; Wed, 21 Jan 2009 09:13:56 -0600 (CST) Date: Wed, 21 Jan 2009 09:13:56 -0600 From: Kenneth Marshall To: Grzegorz Ja??kiewicz Cc: paulo matadr , pgsql-general@postgresql.org, admin Subject: Re: [GENERAL] bytea size limit? Message-ID: <20090121151356.GB28522@it.is.rice.edu> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <2f4958ff0901210555y8b02b8dpa9db2b15873bf23a@mail.gmail.com> <20090121140623.GG14570@it.is.rice.edu> <901365.77018.qm@web52506.mail.re2.yahoo.com> <2f4958ff0901210707v5e639b39of59f678a19981c30@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2f4958ff0901210707v5e639b39of59f678a19981c30@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/89 X-Sequence-Number: 31136 On Wed, Jan 21, 2009 at 03:07:13PM +0000, Grzegorz Ja??kiewicz wrote: > On Wed, Jan 21, 2009 at 3:02 PM, paulo matadr wrote: > > My system have very large ram size, so its possible review postgresql.conf ? > > > all depends on how you access DB, what type of drivers (odbc, libpq, etc, etc). > See, every time you pass a row , they usually have to allocate that > much memory, not only its quite inefficient, but also slow. > > As for the configuration option, I am interested in knowing myself too :) > I do not think that the size limit is a runtime option. It is currently compiled into the server. Ken From mmoncure@gmail.com Wed Jan 21 15:35:50 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E7C4063253D; Wed, 21 Jan 2009 11:35:50 -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 01022-09; Wed, 21 Jan 2009 11:35:46 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f16.google.com (mail-bw0-f16.google.com [209.85.218.16]) by mail.postgresql.org (Postfix) with ESMTP id 36A28632526; Wed, 21 Jan 2009 11:35:40 -0400 (AST) Received: by bwz9 with SMTP id 9so26851bwz.19 for ; Wed, 21 Jan 2009 07:35:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=dUARzCC3zjNWA77MLzXpyEAr2wq9jnWAcXdu1AkQcA0=; b=QbiXD1OycWxVnKyuuIeqWufVkVDH7CX1C9f7OvLIibX1x4ysDBjhk82B6vlMZrrKn1 NdGmid7PrYlE4GfuGIVFKFxlo+zIbgOVal5JyPKfTYLSuJp6SKQEYBtGgWYELTcBi/lO Jf1pLj+F/x8PGvAUy6VDKNCoMyK4/UHsdKMr4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LtuMFMpSGLxtrxoOA9DPv5Yejvt7oSgNh7SXZdRrr0rbtd9bkiiquMpjtMy7nQrefE G0y6i8hyRu2wsqd19s0Vwvego1fqOevNsWwhsv953+wh7Ns7Tq9bpPyjb1fRYUqhQaQ5 bVwS9csGxoVWP9G6tVRguAxN9d0P3LVi9WlUo= MIME-Version: 1.0 Received: by 10.103.24.11 with SMTP id b11mr158477muj.76.1232551922165; Wed, 21 Jan 2009 07:32:02 -0800 (PST) In-Reply-To: <359812.4771.qm@web52512.mail.re2.yahoo.com> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> Date: Wed, 21 Jan 2009 10:32:02 -0500 Message-ID: Subject: Re: [GENERAL] bytea size limit? From: Merlin Moncure To: paulo matadr Cc: pgsql-general@postgresql.org, admin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/95 X-Sequence-Number: 31142 On 1/21/09, paulo matadr wrote: > > I everyone, need help!!! > My aplication return erro: > > 2009-01-20 10:22:03,264 INFO [STDOUT] Caused by: org.postgresql.util. > PSQLException: ERROR: invalid memory alloc request size 1705447581 What exactly were you doing when you got the error? How big is the item? How are you trying to pull it?? libpq, php, etc? merlin From laurenz.albe@wien.gv.at Wed Jan 21 17:03:30 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id C57C36324FB; Wed, 21 Jan 2009 13:03:30 -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 22640-05; Wed, 21 Jan 2009 13:03:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay-fr112.magwien.gv.at (relay-fr112.magwien.gv.at [217.149.225.66]) by mail.postgresql.org (Postfix) with ESMTP id 472AB6324D0; Wed, 21 Jan 2009 13:03:19 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id 448636EFCC; Wed, 21 Jan 2009 18:03:18 +0100 (CET) Received: from exrat0.host.magwien.gv.at (exrat0.host.magwien.gv.at [10.153.0.104]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id 25FB46EFC5; Wed, 21 Jan 2009 18:03:18 +0100 (CET) Received: from exadv11.host.magwien.gv.at ([10.153.17.1]) by exrat0.host.magwien.gv.at with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Jan 2009 18:03:17 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Subject: Re: [GENERAL] bytea size limit? Date: Wed, 21 Jan 2009 18:03:17 +0100 Message-ID: In-Reply-To: <359812.4771.qm@web52512.mail.re2.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [GENERAL] bytea size limit? Thread-Index: Acl76NisV8ot+U+OTuy0Ox+X8VntbAAAP4cg References: <359812.4771.qm@web52512.mail.re2.yahoo.com> From: "Albe Laurenz" To: "paulo matadr *EXTERN*" , , "admin" X-OriginalArrivalTime: 21 Jan 2009 17:03:17.0872 (UTC) FILETIME=[27E60700:01C97BEA] X-Virus-Scanned: by amavisd-new using Sophie and ClamAV at magwien.gv.at X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200901/99 X-Sequence-Number: 31146 cGF1bG8gbWF0YWRyIHdyb3RlOg0KPiBJIGV2ZXJ5b25lLCBuZWVkIGhlbHAhISENCj4gTXkgYXBs aWNhdGlvbiByZXR1cm4gZXJybzoNCj4gDQo+IDIwMDktMDEtMjAgMTA6MjI6MDMsMjY0IElORk8g IFtTVERPVVRdIENhdXNlZCBieTogb3JnLnBvc3RncmVzcWwudXRpbC4NCj4gUFNRTEV4Y2VwdGlv bjogRVJST1I6IGludmFsaWQgbWVtb3J5IGFsbG9jIHJlcXVlc3Qgc2l6ZSAxNzA1NDQ3NTgxDQo+ IA0KPiANCj4gIFRBQkxFIGJhdGNoLnJlbGF0b3Jpb19nZXJhZG8gDQo+IA0KPiAgIHJlZ2VfaWQg aW50ZWdlciBOT1QgTlVMTCwNCj4gICBmdWluX2lkIGludGVnZXIgTk9UIE5VTEwsDQo+ICAgcmVs YV9pZCBpbnRlZ2VyIE5PVCBOVUxMLA0KPiAgIHJlZ2VfdG11bHRpbWFhbHRlcmFjYW8gdGltZXN0 YW1wIHdpdGhvdXQgdGltZSB6b25lIE5PVCBOVUxMIERFRkFVTFQgbm93KCksDQo+ICAgcmVnZV9u bnBhZ2luYXMgaW50ZWdlciBOT1QgTlVMTCwNCj4gICByZWdlX2JpbmFyaW8gYnl0ZWEsDQo+ICAg cmVnZV9wZGYgYnl0ZWENCj4gDQo+IEkgZ2V0IHRoaXMgZXJybyBhYm92ZSAgcmVmZXJzIHRoZSBj b2x1bW4gInJlZ2VfcGRmIGJ5dGVhIiAgICwgDQo+IHdoZW4gdHJ5IGdlbmVyYXRlIHJlcG9ydCBp biBwZGYuDQoNCldoYXQgYXJlIHlvdSBkb2luZyBpbiB0ZXJtcyBvZiBTUUw/DQpJTlNFUlQsIFVQ REFURSwgREVMRVRFPw0KDQpIb3cgYmlnIGFyZSB0aGUgYmluYXJ5IG9iamVjdHMgaW52b2x2ZWQ/ DQoNCldoYXQgYXJlIHRoZSB2YWx1ZXMgb2YgdGhlIGRhdGFiYXNlIHBhcmFtZXRlcnMgc2hhcmVk X2J1ZmZlcnMgYW5kIHdvcmtfbWVtPw0KDQpZb3VycywNCkxhdXJlbnogQWxiZQ0K From laurenz.albe@wien.gv.at Thu Jan 22 09:26:33 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 947536324E0; Thu, 22 Jan 2009 05:26:33 -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 63949-05; Thu, 22 Jan 2009 05:26:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay-fr112.magwien.gv.at (relay-fr112.magwien.gv.at [217.149.225.66]) by mail.postgresql.org (Postfix) with ESMTP id 8A5BA62D9BF; Thu, 22 Jan 2009 05:26:29 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id A5F5C6F0E4; Thu, 22 Jan 2009 10:26:27 +0100 (CET) Received: from exrat0.host.magwien.gv.at (exrat0.host.magwien.gv.at [10.153.0.104]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id 730D26F0A0; Thu, 22 Jan 2009 10:26:27 +0100 (CET) Received: from exadv11.host.magwien.gv.at ([10.153.17.1]) by exrat0.host.magwien.gv.at with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 10:26:27 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Subject: Re: [GENERAL] bytea size limit? Date: Thu, 22 Jan 2009 10:26:26 +0100 Message-ID: In-Reply-To: <874436.25662.qm@web52503.mail.re2.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] [GENERAL] bytea size limit? Thread-Index: Acl78NR+5AmT0jlCR9uhoRBteoTN4AAgalMg References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <874436.25662.qm@web52503.mail.re2.yahoo.com> From: "Albe Laurenz" To: "paulo matadr *EXTERN*" Cc: "GENERAL" , "admin" X-OriginalArrivalTime: 22 Jan 2009 09:26:27.0299 (UTC) FILETIME=[80564330:01C97C73] X-Virus-Scanned: by amavisd-new using Sophie and ClamAV at magwien.gv.at X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200901/113 X-Sequence-Number: 31160 UGxlYXNlIGRvbid0IHRvcCBwb3N0Lg0KDQpwYXVsbyBtYXRhZHIgd3JvdGU6DQo+Pj4gTXkgYXBs aWNhdGlvbiByZXR1cm4gZXJybzoNCj4+PiANCj4+PiAyMDA5LTAxLTIwIDEwOjIyOjAzLDI2NCBJ TkZPICBbU1RET1VUXSBDYXVzZWQgYnk6IG9yZy5wb3N0Z3Jlc3FsLnV0aWwuDQo+Pj4gUFNRTEV4 Y2VwdGlvbjogRVJST1I6IGludmFsaWQgbWVtb3J5IGFsbG9jIHJlcXVlc3Qgc2l6ZSAxNzA1NDQ3 NTgxDQo+Pg0KPj4gV2hhdCBhcmUgeW91IGRvaW5nIGluIHRlcm1zIG9mIFNRTD8NCj4+IElOU0VS VCwgVVBEQVRFLCBERUxFVEU/DQo+PiANCj4+IEhvdyBiaWcgYXJlIHRoZSBiaW5hcnkgb2JqZWN0 cyBpbnZvbHZlZD8NCj4+IA0KPj4gV2hhdCBhcmUgdGhlIHZhbHVlcyBvZiB0aGUgZGF0YWJhc2Ug cGFyYW1ldGVycyBzaGFyZWRfYnVmZmVycyANCj4+IGFuZCB3b3JrX21lbT8NCj4NCj4gVGhlIHNp emUgb2Ygb2JqZWN0IGRlcGVuZCBvbiByZXBvcnQgIGZvciBhIHVzZXIgcmVxdWVzdCwNCj4gc2hh cmVkX2J1ZmZlcnMgPSAyMDQ4TUINCj4gd29ya19tZW0gPSAxMk1CIA0KPiANCj4gLS0tLS0tLQ0K PiBTZXJ2ZXIgY29uZg0KPiAxNiBHQiBSQU0NCj4gUmVkIEhhdCBFbnRlcnByaXNlIExpbnV4IFNl cnZlciByZWxlYXNlIDUNCj4gDQo+IFVzaW5nIGFwbGljY2F0aW9uIHdlYiBiYXNlZCAsIHdpdGgg SmJvc3MgYXBsaWNjYXRpb24gc2VydmVyIG9uIGpkYmMgZHJpdmVyLg0KPiBMZXRzIHNlZSAgc2Nl bmFyaW8gOg0KPiBBcGxpY2NhdGlvbiByZXF1ZXN0IGEgcmVwb3J0LGlmIHRoaXMgYmlnZ2VyICwg aGFuZ3MgLg0KPiBObyBhYmxlIHRvIHNlbGVjdCBvciBvdGhlcnMgcmVwb3J0IGluIHRoaXMgdGFi bGUuDQoNCllvdSBuZWVkIHRvIGZpbmQgb3V0IHRoZSBTUUwgc3RhdGVtZW50IHRoYXQgdHJpZ2dl cnMgdGhlIGVycm9yLg0KDQpUaGUgZXJyb3IgeW91IHF1b3RlZCBkb2VzIG5vdCBjb21lIGZyb20g dGhlIEpEQkMgZHJpdmVyLCBidXQgZnJvbSB0aGUgZGF0YWJhc2UNCnNlcnZlci4NCg0KSSBzdWdn ZXN0IHRoYXQgeW91IHNldA0KbG9nX21pbl9tZXNzYWdlcyB0byBFUlJPUiBvciBsb3dlciwNCmxv Z19taW5fZXJyb3Jfc3RhdGVtZW50IHRvIEVSUk9SIG9yIGxvd2VyLCBhbmQNCmxvZ19zdGF0ZW1l bnQgdG8gYWxsLg0KDQpUaGVuIHJlcHJvZHVjZSB0aGUgZXJyb3IgYW5kIGxvb2sgaW50byB0aGUg bG9nIGZpbGUgdG8gZmluZCBvdXQgdGhlDQpzdGF0ZW1lbnQgdGhhdCBnb3QgdGhlIGVycm9yLiBX ZSBjYW4gcHJvY2VlZCBmcm9tIHRoZXJlLg0KDQpZb3VycywNCkxhdXJlbnogQWxiZQ0K From gryzman@gmail.com Thu Jan 22 13:19:30 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 9A60E63249D; Thu, 22 Jan 2009 09:19:30 -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 14597-07; Thu, 22 Jan 2009 09:19:18 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.159]) by mail.postgresql.org (Postfix) with ESMTP id 816AA632425; Thu, 22 Jan 2009 09:19:18 -0400 (AST) Received: by fg-out-1718.google.com with SMTP id 16so1968585fgg.23 for ; Thu, 22 Jan 2009 05:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=sCdA5bvzIBj1UBlT20abxz8yk5TLiD4/kRojFcrPHpQ=; b=wYO0NEDZ6Tjj+WRkBazM4oI/4g90X+Ta3GL7SB2v9kzpltf5xYZ77AAY8Oy4bN8mDR A2t6y+EyzxN3NB6GZfPKJ+go/ge8kpbM1OEnyDRrx8UEzP+y4/6xVDgA/l4mStQAA96E 8iqqZDlospYbXBiIjCbsOb3jyB5Vhg7cT9+BE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=bXEfptzVh/r+NELIjoAcRLI55+s0sLY4nxMkaaRlpxPc+zKUqNmvvELBgiFG01CmYX JJUfs/b8Y0iLMiWXMQcnYf1K1E8jmK0AROSMG+fG1WtLcOH9NnGIJZ3dxpyh5LTuKYqk +VWcmJkcNLV6jk5y460sips53a3xKc1265CDs= MIME-Version: 1.0 Received: by 10.223.113.199 with SMTP id b7mr51134faq.83.1232630356383; Thu, 22 Jan 2009 05:19:16 -0800 (PST) In-Reply-To: <461902.47623.qm@web52502.mail.re2.yahoo.com> References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <874436.25662.qm@web52503.mail.re2.yahoo.com> <461902.47623.qm@web52502.mail.re2.yahoo.com> Date: Thu, 22 Jan 2009 13:19:16 +0000 Message-ID: <2f4958ff0901220519s4b68c038pb7fe13016b2c8fb1@mail.gmail.com> Subject: Re: [GENERAL] bytea size limit? From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= To: paulo matadr Cc: GENERAL , admin Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit 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/116 X-Sequence-Number: 31163 checkpoints don't have anything to do with it. From laurenz.albe@wien.gv.at Thu Jan 22 16:13:36 2009 Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 87490632A0C; Thu, 22 Jan 2009 12:13:36 -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 10872-04-3; Thu, 22 Jan 2009 12:13:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from relay-fr112.magwien.gv.at (relay-fr112.magwien.gv.at [217.149.225.66]) by mail.postgresql.org (Postfix) with ESMTP id C197E63269A; Thu, 22 Jan 2009 12:09:38 -0400 (AST) Received: from localhost (localhost.localdomain [127.0.0.1]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id 343556EF23; Thu, 22 Jan 2009 17:09:37 +0100 (CET) Received: from exrat0.host.magwien.gv.at (exrat0.host.magwien.gv.at [10.153.0.104]) by relay-fr112.magwien.gv.at (Postfix) with ESMTP id DA6166EFEF; Thu, 22 Jan 2009 17:09:36 +0100 (CET) Received: from exadv11.host.magwien.gv.at ([10.153.17.1]) by exrat0.host.magwien.gv.at with Microsoft SMTPSVC(6.0.3790.3959); Thu, 22 Jan 2009 17:08:33 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Subject: Re: [GENERAL] bytea size limit? Date: Thu, 22 Jan 2009 17:08:32 +0100 Message-ID: In-Reply-To: <461902.47623.qm@web52502.mail.re2.yahoo.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ADMIN] [GENERAL] bytea size limit? Thread-Index: Acl8jg2Ws/kD/pG1SderGh3GZbhYIQAFN28A References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <874436.25662.qm@web52503.mail.re2.yahoo.com> <461902.47623.qm@web52502.mail.re2.yahoo.com> From: "Albe Laurenz" To: "paulo matadr *EXTERN*" Cc: "GENERAL" , "admin" X-OriginalArrivalTime: 22 Jan 2009 16:08:33.0546 (UTC) FILETIME=[ACB366A0:01C97CAB] X-Virus-Scanned: by amavisd-new using Sophie and ClamAV at magwien.gv.at X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200901/121 X-Sequence-Number: 31168 UGxlYXNlIGRvbid0IHRvcCBwb3N0Lg0KDQpwYXVsbyBtYXRhZHIgd3JvdGU6DQo+IEkgdGhpbmsg aWRlbnRpZmllZCB0aGUgcHJvYmxlbQ0KPiBsdHMncyBjaGVjayBsb2cgYmVsb3c6DQo+IA0KPiBR dWVyeToNCj4gU0VMRUNUU1RBVEVNRU5UOiAgc2VsZWN0IHJlbGF0b3Jpb3MwXy5mdWluX2lkIGFz IGZ1aW41XzFfLCByZWxhdG9yaW9zMF8ucmVnZV9pZCBhcyByZWdlMV8xXywgcmVsYXRvcmlvczBf LnJlZ2VfaWQgYXMgcg0KPiBlZ2UxXzYyNF8wXywgcmVsYXRvcmlvczBfLnJlZ2VfdG11bHRpbWFh bHRlcmFjYW8gYXMgcmVnZTJfNjI0XzBfLCByZWxhdG9yaW9zMF8ucmVnZV9ubnBhZ2luYXMgYXMg cmVnZTNfNjI0XzBfLCByZWxhdG9yaW9zMF8ucmVnZV9wZGYgYXMgcmVnZTRfNjI0XzBfLCByZWxh dG9yaW9zMF8uZnVpbl9pZCBhcyBmdWkNCj4gbjVfNjI0XzBfLCByZWxhdG9yaW9zMF8ucmVsYV9p ZCBhcyByZWxhNl82MjRfMF8gZnJvbSBiYXRjaC5yZWxhdG9yaW9fZ2VyYWRvIHJlbGF0b3Jpb3Mw XyB3aGVyZSByZWxhdG9yaW9zMF8uZnVpbl9pZCBpbiAoJDEsICQyKQ0KPiAgDQo+IEVycm9yOg0K PiAyMDA5LTAxLTE4IDAwOjA1OjI4IEJSVCBMT0c6ICBjaGVja3BvaW50cyBhcmUgb2NjdXJyaW5n IHRvbyBmcmVxdWVudGx5ICgyNSBzZWNvbmRzIGFwYXJ0KQ0KPiAyMDA5LTAxLTE4IDAwOjA1OjI4 IEJSVCBISU5UOiAgQ29uc2lkZXIgaW5jcmVhc2luZyB0aGUgY29uZmlndXJhdGlvbiBwYXJhbWV0 ZXIgImNoZWNrcG9pbnRfc2VnbWVudHMiLg0KPiBnc2FuX2NvbWVyY2lhbCBnY29tX2JhdGNoIDEw LjEuMS41IDIwMDktMDEtMTggMDA6MDU6MzkgQlJUIFNFTEVDVEVSUk9SOiAgaW52YWxpZCBtZW1v cnkgYWxsb2MgcmVxdWVzdCBzaXplIDE3MDU0NDc1ODENCg0KPiB3ZSAgbmVlZCBtYWtlIHJlcG9y dCBiaWdnZXIgdGhhbiAyMDAgTS4NCj4gc3VnZ2VzdGlvbnM/DQoNCkkgdHJpZWQgc2VsZWN0aW5n IGxhcmdlIGJ5dGVhIHZhbHVlcyBvbiBteSA4LjMuNSBzeXN0ZW0sIGFuZA0KSSByYW4gaW50byBz aW1pbGFyIHByb2JsZW1zOyBJIGNvdWxkIHNlbGVjdCBhIHZhbHVlIG9mIGxlbmd0aCAyMDAwMDAw MDANCmJ1dCBnb3QgdGhlIHNhbWUgZXJyb3Igd2l0aCBhIHZhbHVlIG9mIDI2ODQzNTQ1NiBieXRl cy4NCg0KSSB0cmllZCB3aXRoIHBzcWwuDQoNCkFueW9uZSBrbm93cyB3aGF0IGNhdXNlcyB0aGlz Pw0KDQpJIGd1ZXNzIGl0IG1pZ2h0IGJlIHRoZSBiZXN0IGFwcHJvYWNoIGZvciB5b3UgdG8gZWl0 aGVyIHVzZSBsYXJnZSBvYmplY3RzLA0Kd2hpY2ggY2FuIGNvbnRhaW4gdXAgdG8gMkdCIGFuZCBw cm92aWRlIGZ1bmN0aW9ucyB0byByZWFkIHRoZW0gaW4gc21hbGxlciBwYXJ0cywNCm9yIHRvIGNo YW5nZSB5b3VyIHRhYmxlIHN0cnVjdHVyZSBzbyB0aGF0IGxhcmdlIHZhbHVlcyBhcmUgc3BsaXQg aW50bw0KcGFydHMgYW5kIHN0b3JlZCBzZXBhcmF0ZWx5Li4uDQoNCllvdXJzLA0KTGF1cmVueiBB bGJlDQo=