Depends what the default is on your system. The default is 5% with the
version of mke2fs that I have here, so you would just:
tune2fs -m 5 <devicename>
to put it back.
On Thu, 27 Jul 2006, Erik Jones wrote:
Awesome. Do I need to reset that to any magic # after the vacuum? I'm not
all that up on filesystem maintenance/tweaking...
Scott Marlowe wrote:
I can't tell you the number of times that little trick has saved my
life.
On Thu, 2006-07-27 at 11:32, Jeff Frost wrote:
You can probably just "tune2fs -m 0 <device name>" to give yourself enough
space to get out of the jam before you go deleting things. Then you might
want to vacuum full afterwards.
On Thu, 27 Jul 2006, Erik Jones wrote:
Hello, quick question. I've run into an issue with the disk that my
development box is on filling up and preventing pretty much any writing
(inserts, updates, deletes, etc...) from happening. Other than some
piddly text logs the db is pretty much the only thing on the box. So, my
question is: what can I do to free space and run a full vacuum? (I was
not the one who set up this box and there has been virtually no
administration or maintenance on it that I know of...) How about the WAL
files in pg_xlog? How critical are they when no data on the system is
critical in and of itself? Any suggestions would be greatly
appreciated...
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
--
Jeff Frost, Owner <[EMAIL PROTECTED]>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
