Alex,
Thanks for the explanation. That helps.
After looking at some of the pgsql_tmp files, It was clear we needed to
increase work_mem. So I switched back to the pgtune suggestions with one
change:
-bash-3.2$ diff postgresql.conf postgresql.conf.local | grep
log_temp_files = 0
On Wed, Jul 28, 2010 at 15:43, Irene Barg ib...@noao.edu wrote:
Alex,
The postmaster wouldn't start with shared_buffers = 5632MB, so we reduced it
to 2GB. The system's shared memory is:
[dpp...@pipen18 ~]$ sudo /sbin/sysctl -a | grep kernel | grep shmmax
kernel.shmmax = 4182863872
You can
Alex,
It's funny how one cannot see what is right in front of them. I did NOT
notice that 'var' was mounted as '/var/log', so postgres was getting
installed in root '/'. So I moved pgsql to /data1, and created a symlink
in /var/lib/pgsql to /data1/pgsql.
Now I have a pgsql_tmp file that
On Tue, Jul 27, 2010 at 15:58, Irene Barg ib...@noao.edu wrote:
I'm afraid I don't understand how turning on 'log_temp_files' will help?
Well, postgres is probably doing exactly what its told. You just need
to figure out what that is and why. ( and if it is some kind of bug,
we wont be able to
System info: Lancelot 1874-T dual Intel Xeon(Nehalem-DP) SATAII 24GB
RAM, CentOS release 5.4 (Final), postgresql-server-8.4.4-1PGDG
hi,
We installed a fresh version of postgresql-server-8.4.4-1 using RPMs
from PGDG. We are seeing the following errors, if the system trys to do
'anything' sort
On Mon, Jul 26, 2010 at 16:01, Irene Barg ib...@noao.edu wrote:
2010-07-26 11:33:33 MST system_admin metadataERROR: could not write block
503414 of temporary file: No space le
ft on device
2010-07-26 11:33:33 MST system_admin metadataHINT: Perhaps out of disk
space?
-bash-3.2$ df -h
Alex Hunsaker bada...@gmail.com writes:
On Mon, Jul 26, 2010 at 16:01, Irene Barg ib...@noao.edu wrote:
2010-07-26 11:33:33 MST system_admin metadataERROR: Â could not write block
503414 of temporary file: No space le
ft on device
2010-07-26 11:33:33 MST system_admin metadataHINT: Â Perhaps
