Ben Kim wrote:
Just curious, I guess the problem is not simply the disk full now, but supposing the disk full is the only problem, what would happen if we move some old files temporarily from pg_xlog/* to somewhere else and free up some disk space? (On mine, I guess I can get about 75 MB, leaving the most recent ones: say, dated today.)
Uhmmm don't do that :). You need to find something else. The pg_xlog is your transaction logs.
I tried su - postgres -c '/apps/pgsql-7.4/bin/pg_ctl stop -D /data/postgres/gex_runtime -m immediate' on one of the two hozed servers and that's (I think) what got this:---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not matchRegards, Ben Kim Developer http://benix.tamu.edu ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
-- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl - http://www.commandprompt.com/
