-
1. Re: PostgreSQL ERROR: canceling statement due to statement timeout
pilhuhn Dec 24, 2009 5:36 AM (in response to rstephan)1 of 1 people found this helpfulRichard,
what version of JBossON/Jopr/RHQ are you using?
Heiko
-
2. Re: PostgreSQL ERROR: canceling statement due to statement timeout
rstephan Dec 24, 2009 10:14 AM (in response to pilhuhn)JON version 2.3.0.GA
The JON is running on Solaris 10 zone but I am not sure which version of JBoss it is running within.
PostgreSQL 8.3.9 on Solaris 10
-
3. Re: PostgreSQL ERROR: canceling statement due to statement timeout
rstephan Jan 7, 2010 1:25 PM (in response to rstephan)Change the work_mem database parameter from 2MB to 16MB. All of the disk I/O needed for the hash join and group by is moved to memory instead. This is where the bottleneck was coming from. Warning: Make sure you have enough system memory to perform this. Every database connection gets its own memory, and so if you have 32 connections that would consume 512MB instead of 64MB.
-
4. Re: PostgreSQL ERROR: canceling statement due to statement timeout
rstephan Jan 7, 2010 1:34 PM (in response to rstephan)Accidently pushed the question was answered. Oh well. -
5. Re: PostgreSQL ERROR: canceling statement due to statement timeout
pilhuhn Jan 8, 2010 4:24 AM (in response to rstephan)Richard,
this is a great finding (and so obvious after one knows the solution)!
It looks like Postgres is able to have this set per connection, so we could just set it before starting the baseline computation:
postgres=# set work_mem=32768;
SET
postgres=# show work_mem;
work_mem
----------
32MB
(1 row)
I have opened the following Bugzilla to track this: Bug 553561