I think identified the problem
lts's check log below:
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)
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
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?
suggestions?
De: Albe Laurenz <laurenz.albe@xxxxxxxxxx>
Para: paulo matadr *EXTERN* <saddoness@xxxxxxxxxxxx>
Cc: GENERAL <pgsql-general@xxxxxxxxxxxxxx>; admin <pgsql-admin@xxxxxxxxxxxxxx>
Enviadas: Quinta-feira, 22 de Janeiro de 2009 6:26:26
Assunto: Re: [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@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Veja quais são os assuntos do momento no Yahoo! + Buscados: Top 10 - Celebridades - Música - Esportes
