Greg, I'm not sure what you're looking for in the way of suggestions. Do you just want to be able to start this postgres server up and remove some data? Easiest way I see to accomplish that given the information you provided is to move pg_xlog to the sda disk and symlink it to the data dir. In general terms, it would go like this: Stop postmaster cd /data/gex_runtime mv pg_xlog / ln -s /pg_xlog Start postmaster The commands may vary depending on OS. That would also give you better performance if sda and sdb are actually separate physical disks. However, that's only going to give you about 500MB of free space, so I see bigger disks in your future. A vacuum full might recover a bit of space as well if you've got any bloat. The question I have is this: Is your database read-only? Otherwise, bringing these machines back up probably isn't too useful as they are now out of sync with the new primary (your old hot spare). Good luck! -----Original Message----- From: pgsql-admin-owner@xxxxxxxxxxxxxx [mailto:pgsql-admin-owner@xxxxxxxxxxxxxx] On Behalf Of Gregory S. Williamson Sent: Sunday, January 01, 2006 11:28 PM To: pgsql-admin@xxxxxxxxxxxxxx Subject: [ADMIN] full data disk -- any chance of recovery Availables space is: $ df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 32850580 3137552 28044280 11% / /dev/sdb1 35001508 33223500 16 100% /data Any suggestions ? Falling back to the last known state is fine, but just in case I am making a backup of the remaining database to build a replacement. And yes, I did forsee this and did warn management repeatedly and yet somehow the advice falls on deaf ears. Go figure. I guess maybe because it isn't management that a hole kicked in a 3 day weekend.
