RE: [cobalt-users] Moving PostgreSQL

["James Hurst" <james@xxxxxxxxxxxxxxxxxxxxxxxx>]

> 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.
>
> 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.

Yeah, I am (now) aware of that, although the fact that postgres was a
'feature' of the system was one of the reasons why I bought it. I followed
the instructions carefully, and postgres seems to be working fine, and so I
don't think the GUI could be at risk.

My main reason for going with postgres over mysql is transaction support,
which I believe is only a very new feature in mysql. That the system is
built using transactions is a prerequisite that the client (a uk government
division) has specified.

So, do you or anyone have any advice over and above shutting down postgres,
copying the contents of /var/lib/pgsql to /home/pgsql, setting up a hard
link and restarting the service?

I'd be interested if anyone has actually tried this.

> 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.

Fortunately, everything is at the development stage, so nothing other than
any inconvenience it may cause to the development schedule is at risk.

Cheers.

James Hurst.
// mailto:james@xxxxxxxxxxxxxxxxxxxxxxxx
// "..in a world without boundaries or fences, who
// needs Gates anyway?"