Please don't top post.
paulo matadr wrote:
> I think identified the problem
> lts's check log below:
> 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)
> 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
> we need make report bigger than 200 M.
I tried selecting large bytea values on my 8.3.5 system, and
I ran into similar problems; I could select a value of length 200000000
but got the same error with a value of 268435456 bytes.
I tried with psql.
Anyone knows what causes this?
I guess it might be the best approach for you to either use large objects,
which can contain up to 2GB and provide functions to read them in smaller parts,
or to change your table structure so that large values are split into
parts and stored separately...
In response to
pgsql-admin by date
|Next:||From: Isabella Ghiurea||Date: 2009-01-22 17:39:22|
|Subject: pgbouncer compilation errors|
|Previous:||From: Carol Walter||Date: 2009-01-22 15:35:22|
|Subject: ssl database connection problems...|
pgsql-general by date
|Next:||From: Alvaro Herrera||Date: 2009-01-22 16:16:46|
|Subject: Re: difference between current_timestamp and now() inquotes|
|Previous:||From: Raymond O'Donnell||Date: 2009-01-22 15:59:22|
|Subject: Re: difference between current_timestamp and now() in quotes|