Re: [PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24

2014-06-19 7:35 GMT+02:00 Huang, Suya : > From: Pavel Stehule [mailto:pavel.steh...@gmail.com] > Sent: Thursday, June 19, 2014 3:28 PM > To: Huang, Suya > Cc: pgsql-performance@postgresql.org > Subject: Re: [PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24 > > Hello > > The size of statfile is

Re: [PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24

From: Pavel Stehule [mailto:pavel.steh...@gmail.com] Sent: Thursday, June 19, 2014 3:28 PM To: Huang, Suya Cc: pgsql-performance@postgresql.org Subject: Re: [PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24 Hello The size of statfile is related to size of database objects in database. Depend

Re: [PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24

Hello The size of statfile is related to size of database objects in database. Depends on PostgreSQL version this file can be one per database cluster or one per database (from 9.3), These statistics should by reset by call pg_stat_reset() http://www.postgresql.org/docs/9.2/static/monitoring-sta

[PERFORM] huge pgstat.stat file on PostgreSQL 8.3.24

Hi group, We've found huge pgstat.stat file on our production DB boxes, the size is over 100MB. autovacuum is enabled. So my question would be: 1. What's a reasonable size of pgstat.stat file, can it be estimated? 2. What's the safest way to reduce the file size to alleviate the IO

Re: [PERFORM] Unable to allocate 2G of shared memory on wheezy

Dave Cramer writes: > 2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory: > Cannot allocate memory > 2014-06-18 13:37:15 EDT HINT: This error usually means that PostgreSQL's > request for a shared memory segment exceeded available memory or swap > space. To reduce the request s

Re: [PERFORM] Unable to allocate 2G of shared memory on wheezy

Problem solved... a runaway process (puppet) had consumed all available real memory Dave Cramer On 18 June 2014 15:24, Dave Cramer wrote: > 2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory: > Cannot allocate memory > 2014-06-18 13:37:15 EDT HINT: This error usually means

Re: [PERFORM] Unable to allocate 2G of shared memory on wheezy

2014-06-18 13:37:15 EDT FATAL: could not map anonymous shared memory: Cannot allocate memory 2014-06-18 13:37:15 EDT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory or swap space. To reduce the request size (currently 8826445824 bytes

Re: [PERFORM] Unable to allocate 2G of shared memory on wheezy

Dave Cramer writes: > To reduce the request size [FAILently 2232950784 bytes), reduce > PostgreSQL's shared memory usage, This error message is a bit garbled :-(. It would've been useful to know the specific errno, but you've trimmed out that info. Perhaps it's failing because you already have

[PERFORM] Unable to allocate 2G of shared memory on wheezy

Here are my kernel settings kernel.shmmax = 10737418240 # Maximum total size of all shared memory segments in pages (normally 4096 bytes) kernel.shmall = 2621440 kernel.sem = 250 32000 32 1200 They are actually set... sysctl -a | grep shm kernel.shmmax = 10737418240 kernel.shmall = 2621440 kern