[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Moving PostgreSQL



"Gavin Nelmes-Crocker" <cobalt@xxxxxxxxxxxxxxxx> wrote:
> > Can I simply move everything and create a sym link from /var/lib/pgsql
to
> > /home/pgsql??
>
> James I don't know what doing that will do - but bear in mind the postgres
> database is on there for the GUI and admin purposes and for no other
reason.
> The fact that you can access it and use it in some ways a risk - if it is
> one you are happy to take carry on.

Why not shutdown PostgreSQL, backup the directory, move the original to the
new location, create the symlink, restart PostgreSQL and see what happens?
If it doesn't work, undo the changes and put the directory back in its
original location.  That would be a whole lot faster than asking here and
waiting and there's not really any risk.

> My Advice to you would be to move your database over to MySQL and keep it
> separate from the GUI and admin functions altogether, you are only asking
> for pain.

I assume Gavin had a reason for selecting PostgreSQL over MySQL.  There are
definitely software applications where it's a better fit.  If you don't want
to use the pre-installed PostgreSQL because you're worried that it might
affect the GUI or you want to compile a newer version of PostgreSQL with
different features, install a second copy and use it for your project.  Just
configure it to run on a different port and use a different socket file.

> Bear in mind if you try this don't do it with a live box and you may kill
> it - several people on this list have had to rebuild the database on RaQ3
> and 4 and there are some scripts to help but I don't know if any of them
> have ever done it on an XTR so boldly go.

FUD.  Creating a symlink will either work or it won't.  It won't corrupt the
Cobalt database.  I've run many databases from the Cobalt install of
PostgreSQL both for myself and clients with no problems.  I've also
installed additional copies of PostgreSQL, stable and development versions
of MySQL, all with good results.  YMMV.  And as long as you generate good
frequent backups a corrupted PostgreSQL database or problem with any file on
the server is really a minor hiccup (there's some subtle advise here).

--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/