From: | John R Pierce <pierce(at)hogranch(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: safelly erasing dirs/files |
Date: | 2009-11-15 07:30:33 |
Message-ID: | 4AFFAE19.7080803@hogranch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Greg Smith wrote:
>> how do I un-bloat the /var partition ? this is why I was considering
>> rm !!!!
>>
> I've gotten out of this situation before by finding other files in
> /var to delete, using something like this to figure out where the big
> stuff was at:
while sometimes /var/log or /var/spool data is the problem, far more
often, /var/lib/pgsql/data was the biggun on systems that didn't plan
for this...
my fix has been what I said earlier. in more detail
1) (make available a new storage volume)
2) # mkfs /dev/sd??
3) # mount /dev/sd?? /u01
4) # /etc/init.d/postgresql stop
5) # mv /var/lib/pgsql /u01
7) # ln -s /u01/pgsql /var/lib/pgsql
8) # /etc/init.d/postgresql start
adjust directories and stop/start commands as appropriate for your
distribution.
if you can't come up with a new volume, but have an existing volume with
sufficient space, then...
1) # mkdir /someplace/pgsql
2) # /etc/init.d/postgresql stop
3) # mv /var/lib/pgsql /someplace
4) # ln -s /someplace/pgsql /var/lib/pgsql
5) # /etc/init.d/postgresql start
Personally, I really like having my database data on dedicated RAID10
volumes for best performance.
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2009-11-15 08:34:51 | Re: re-using RETURNING |
Previous Message | undisclosed user | 2009-11-15 06:28:22 | Experience with many schemas vs many databases |