Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id E61DC632581 for ; Thu, 22 Jan 2009 08:36:27 -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 67664-09 for ; Thu, 22 Jan 2009 08:36:23 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from web52502.mail.re2.yahoo.com (web52502.mail.re2.yahoo.com [206.190.48.185]) by mail.postgresql.org (Postfix) with SMTP id 4E3046324E0 for ; Thu, 22 Jan 2009 08:36:22 -0400 (AST) Received: (qmail 48031 invoked by uid 60001); 22 Jan 2009 12:36:21 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.br; h=X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Message-ID; b=tin6GycBbCSeSzvVOt7ujR7+kdpy5pjGkpDAiJpveZ5kW23R3iBV/qdpcSntkfUY+uZD+UX3MGfkQDczJtBsuCaxoJQl5OJosrm1cJJ4Rw4eFUsUlLkqbhNBkBdIVDPu4VIx4vMngmJ0voyu91XYgsDI6DUeRR4JtJP7U48DtDM=; X-YMail-OSG: XU40NVMVM1nzOFXahtXawisglh0UQmPYgrDgj6MvF362owEg6QLJAufAz6vWsXIvgtkCobqilLHWRLM7kWjwGlFlTcZzlSzE5F3oFz3DcwMPk81bJ7QLBFOO9bziOzkqeuRqxiBFfoRUAI_y2.iANUa3FUoA_QLZ0kD7olhxaq7AXywkji3w0MOBmLVqh8Csy_wYaXmlRqip7gGQBg-- Received: from [189.17.249.3] by web52502.mail.re2.yahoo.com via HTTP; Thu, 22 Jan 2009 04:36:21 PST X-Mailer: YahooMailRC/1155.45 YahooMailWebService/0.7.260.1 References: <359812.4771.qm@web52512.mail.re2.yahoo.com> <874436.25662.qm@web52503.mail.re2.yahoo.com> Date: Thu, 22 Jan 2009 04:36:21 -0800 (PST) From: paulo matadr Subject: Res: [GENERAL] bytea size limit? To: Albe Laurenz Cc: GENERAL , admin MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1947800891-1232627781=:47623" Message-ID: <461902.47623.qm@web52502.mail.re2.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200901/114 X-Sequence-Number: 31161 --0-1947800891-1232627781=:47623 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable I think identified the problem=0Alts's check log below:=0A=0AQuery:=0ASELEC= TSTATEMENT: select relatorios0_.fuin_id as fuin5_1_, relatorios0_.rege_id = =0Aas rege1_1_, relatorios0_.rege_id as r=0Aege1_624_0_, =0Arelatorios0_.re= ge_tmultimaalteracao as rege2_624_0_, relatorios0_.rege_nnpaginas =0Aas reg= e3_624_0_, relatorios0_.rege_pdf as rege4_624_0_, relatorios0_.fuin_id as = =0Afui=0An5_624_0_, relatorios0_.rela_id as rela6_624_0_ from =0Abatch.rela= torio_gerado relatorios0_ where relatorios0_.fuin_id in ($1, $2)=0A =0AErro= r:=0A2009-01-18 00:05:28 BRT LOG: checkpoints are occurring too =0Afrequen= tly (25 seconds apart)=0A2009-01-18 00:05:28 BRT HINT: Consider =0Aincreas= ing the configuration parameter "checkpoint_segments".=0Agsan_comercial =0A= gcom_batch 10.1.1.5 2009-01-18 00:05:39 BRT SELECTERROR: invalid memory al= loc =0Arequest size 1705447581=0A=0A=0AAtual parameter postgresql.conf=0A#c= heckpoint_segments =3D 3 # in logfile =0Asegments, min 1, 16= MB each=0A#checkpoint_timeout =3D 5min # range =0A30s-1h=0A#ch= eckpoint_warning =3D 30s # 0 is off=0A#wal_buffers =3D 64kB = # min 32kB=0A =0Awe need make report bigger than 200 M.= =0Asuggestions?=0A=0A=0A=0A=0A=0A________________________________=0ADe: Alb= e Laurenz =0APara: paulo matadr *EXTERN* =0ACc: GENERAL ; admin =0AEnviadas: Quinta-feira, 22 de Janeiro de 2009 6:26= :26=0AAssunto: Re: [ADMIN] [GENERAL] bytea size limit?=0A=0APlease don't to= p post.=0A=0Apaulo matadr wrote:=0A>>> My aplication return erro:=0A>>> =0A= >>> 2009-01-20 10:22:03,264 INFO [STDOUT] Caused by: org.postgresql.util.= =0A>>> PSQLException: ERROR: invalid memory alloc request size 1705447581= =0A>>=0A>> What are you doing in terms of SQL?=0A>> INSERT, UPDATE, DELETE?= =0A>> =0A>> How big are the binary objects involved?=0A>> =0A>> What are th= e values of the database parameters shared_buffers =0A>> and work_mem?=0A>= =0A> The size of object depend on report for a user request,=0A> shared_bu= ffers =3D 2048MB=0A> work_mem =3D 12MB =0A> =0A> -------=0A> Server conf=0A= > 16 GB RAM=0A> Red Hat Enterprise Linux Server release 5=0A> =0A> Using ap= liccation web based , with Jboss apliccation server on jdbc driver.=0A> Let= s see scenario :=0A> Apliccation request a report,if this bigger , hangs .= =0A> No able to select or others report in this table.=0A=0AYou need to fin= d out the SQL statement that triggers the error.=0A=0AThe error you quoted = does not come from the JDBC driver, but from the database=0Aserver.=0A=0AI = suggest that you set=0Alog_min_messages to ERROR or lower,=0Alog_min_error_= statement to ERROR or lower, and=0Alog_statement to all.=0A=0AThen reproduc= e the error and look into the log file to find out the=0Astatement that got= the error. We can proceed from there.=0A=0AYours,=0ALaurenz Albe=0A=0A-- = =0ASent via pgsql-admin mailing list (pgsql-admin@postgresql.org)=0ATo make= changes to your subscription:=0Ahttp://www.postgresql.org/mailpref/pgsql-a= dmin=0A=0A=0A=0A Veja quais s=C3=A3o os assuntos do momento no Yahoo! = +Buscados=0Ahttp://br.maisbuscados.yahoo.com --0-1947800891-1232627781=:47623 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
I think identified the problem
lts's check log below:
Query:
SELECTSTATEMENT:  select relatorios0_.fuin_id as fuin5_1_,= relatorios0_.rege_id =0Aas rege1_1_, relatorios0_.rege_id as r
ege1_624= _0_, =0Arelatorios0_.rege_tmultimaalteracao as rege2_624_0_, relatorios0_.r= ege_nnpaginas =0Aas rege3_624_0_, relatorios0_.rege_pdf as rege4_624_0_, re= latorios0_.fuin_id as =0Afui
n5_624_0_, relatorios0_.rela_id as rela6_62= 4_0_ from =0Abatch.relatorio_gerado relatorios0_ where relatorios0_.fuin_id= in ($1, $2)
=0A
 
=0A
Err= or:
2009-01-18 00:05:28 BRT LOG:  checkpoints are occurring too =0A= frequently (25 seconds apart)
2009-01-18 00:05:28 BRT HINT:  Consid= er =0Aincreasing the configuration parameter "checkpoint_segments".
gsan= _comercial =0Agcom_batch 10.1.1.5 2009-01-18 00:05:39 BRT SELECTERROR: = ; invalid memory alloc =0Arequest size 1705447581


Atual paramete= r postgresql.conf

#checkpoint_segments =3D 3  &n= bsp;            = ; # in logfile =0Asegments, min 1, 16MB each
#checkpoint_timeout =3D 5mi= n            &n= bsp; # range =0A30s-1h
#checkpoint_warning =3D 30s   &nbs= p;           # 0 is off
#wal_buffers =3D 64kB      &nb= sp;            =   # min 32kB
 
we  need make report bigger than 200 M.suggestions?



De: = Albe Laurenz <laurenz.albe@wien.gv.at>
Para: paulo matadr *EXTERN* <saddoness@yahoo.com.= br>
Cc: GENERAL <= pgsql-general@postgresql.org>; admin <pgsql-admin@postgresql.org>
Enviadas: Quinta-feira, 22 de Janeiro de 2009 6:26:26Assunto: Re: [ADMIN] [GEN= ERAL] bytea size limit?

Please don't top post.

paulo m= atadr wrote:
>>> My aplication return erro:
>>> >>> 2009-01-20 10:22:03,264 INFO  [STDOUT] Caused by: org.po= stgresql.util.
>>> PSQLException: ERROR: invalid memory alloc r= equest size 1705447581
>>
>> What are you doing in terms = of SQL?
>> INSERT, UPDATE, DELETE?
>>
>> How bi= g are the binary objects involved?
>>
>> What are the va= lues of the database parameters shared_buffers
>> and work_mem?>
> The size of object depend on report  for a user request= ,
> shared_buffers =3D 2048MB
> work_mem =3D 12MB
>
> -------
> Server conf
> 16 GB RAM
> Red Hat Ent= erprise Linux Server release 5
>
> Using apliccation web based= , with Jboss apliccation server on jdbc driver.
> Lets see  sce= nario :
> Apliccation request a report,if this bigger , hangs .
&g= t; No able to select or others report in this table.

You need to fin= d out the SQL statement that triggers the error.

The error you quote= d does not come from the JDBC driver, but from the database
server.
<= br>I suggest that you set
log_min_messages to ERROR or lower,
log_min= _error_statement to ERROR or lower, and
log_statement to all.

The= n reproduce the error and look into the log file to find out the
stateme= nt that got the error. We can proceed from there.

Yours,
Laurenz = Albe

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)=
To make changes to your subscription:
http://www.postgresql.org/ma= ilpref/pgsql-admin

=0A=0A=0A
Veja quais s=C3=A3o os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - M=C3=BAsica - Esportes --0-1947800891-1232627781=:47623--