Skip site navigation (1) Skip section navigation (2)

Res: [GENERAL] bytea size limit?

From: paulo matadr <saddoness(at)yahoo(dot)com(dot)br>
To: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: GENERAL <pgsql-general(at)postgresql(dot)org>, admin <pgsql-admin(at)postgresql(dot)org>
Subject: Res: [GENERAL] bytea size limit?
Date: 2009-01-22 12:36:21
Message-ID: 461902.47623.qm@web52502.mail.re2.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-general
I think identified the problem
lts's check log below:

Query:
SELECTSTATEMENT:  select relatorios0_.fuin_id as fuin5_1_, relatorios0_.rege_id 
as rege1_1_, relatorios0_.rege_id as r
ege1_624_0_, 
relatorios0_.rege_tmultimaalteracao as rege2_624_0_, relatorios0_.rege_nnpaginas 
as rege3_624_0_, relatorios0_.rege_pdf as rege4_624_0_, relatorios0_.fuin_id as 
fui
n5_624_0_, relatorios0_.rela_id as rela6_624_0_ from 
batch.relatorio_gerado relatorios0_ where relatorios0_.fuin_id in ($1, $2)
 
Error:
2009-01-18 00:05:28 BRT LOG:  checkpoints are occurring too 
frequently (25 seconds apart)
2009-01-18 00:05:28 BRT HINT:  Consider 
increasing the configuration parameter "checkpoint_segments".
gsan_comercial 
gcom_batch 10.1.1.5 2009-01-18 00:05:39 BRT SELECTERROR:  invalid memory alloc 
request size 1705447581


Atual parameter postgresql.conf
#checkpoint_segments = 3                # in logfile 
segments, min 1, 16MB each
#checkpoint_timeout = 5min              # range 
30s-1h
#checkpoint_warning = 30s               # 0 is off
#wal_buffers = 64kB                     # min 32kB
 
we  need make report bigger than 200 M.
suggestions?





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

Please don't top post.

paulo matadr wrote:
>>> 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 are you doing in terms of SQL?
>> INSERT, UPDATE, DELETE?
>> 
>> How big are the binary objects involved?
>> 
>> What are the values of the database parameters shared_buffers 
>> and work_mem?
>
> The size of object depend on report  for a user request,
> shared_buffers = 2048MB
> work_mem = 12MB 
> 
> -------
> Server conf
> 16 GB RAM
> Red Hat Enterprise Linux Server release 5
> 
> Using apliccation web based , with Jboss apliccation server on jdbc driver.
> Lets see  scenario :
> Apliccation request a report,if this bigger , hangs .
> No able to select or others report in this table.

You need to find out the SQL statement that triggers the error.

The error you quoted does not come from the JDBC driver, but from the database
server.

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.

Then reproduce the error and look into the log file to find out the
statement that got the error. We can proceed from there.

Yours,
Laurenz Albe

-- 
Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



      Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com

In response to

Responses

pgsql-admin by date

Next:From: Jan-Peter.SeifertDate: 2009-01-22 12:53:28
Subject: PostgreSQL's query caching behaviour
Previous:From: Albe LaurenzDate: 2009-01-22 09:26:26
Subject: Re: [GENERAL] bytea size limit?

pgsql-general by date

Next:From: Grzegorz JaśkiewiczDate: 2009-01-22 13:19:16
Subject: Re: [GENERAL] bytea size limit?
Previous:From: Igor KatsonDate: 2009-01-22 12:10:59
Subject: Re: [Plproxy-users] A complex plproxy query

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group