On Aug 31, 2007, at 8:35 AM, Phoenix Kiula wrote:
> Thanks everyone. Yes, /var was full because of the backups that're
> going there.
> Database is back working.
> It was my backup script. It is set to save a daily backup to the /var/
> folder, which is not clever. I'll change it to be in the "backup"
> folder which is a mounted one.
> On that note, is it recommended to store the data of the database on a
> different hard disk than the one on which the database is running? How
> can I change the data folder for a live database?
> Many thanks!
The data directory is where the database is "running". If you're
referring to where the postgres binaries are, it doesn't matter as
they are loaded into memory when the server starts. As far as moving
the data directory goes, you can't move it for a running database.
All of the options to move a server's data directory involve, at some
point, shutting down the db. Alternatively, if you're running out of
space on the disk currently holding the data, you can add another
drive in a new tablespace.
Software Developer | Emma®
800.595.4401 or 615.292.5888
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
In response to
pgsql-general by date
|Next:||From: Erik Jones||Date: 2007-08-31 16:05:45|
|Subject: Re: Obtaining random rows from a result set|
|Previous:||From: Decibel!||Date: 2007-08-31 15:49:08|
|Subject: Re: [GENERAL] Undetected corruption of table files|