From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | Andrew Watkins <andrew(at)cse(dot)msstate(dot)edu> |
Cc: | pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Linux cluster application |
Date: | 2006-03-02 20:44:42 |
Message-ID: | 1141332282.18820.97.camel@state.g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, 2006-03-02 at 14:41, Andrew Watkins wrote:
> I'm writing a parallel/distributed application that assesses the
> performance impact of frequent insertions/selects to databases on
> parallel file systems in a linux cluster environment. Currently, the
> application calls for a database server to be running on each node of
> the cluster. Since my end-users may or may not have root access to the
> machines in the various clusters being used, I'm installing postgres
> from within the user's account to facilitate the starting and stopping
> of the postmaster without the need of root access. My general question
> is if anyone has experience with such a situation where the database
> server would need to be started on each machine in a parallel
> environment. If so, are there any suggestions for working with such a
> condition?
You could set up ssh keys with no passphrase and use ssh to do it in a
short shell script.
From | Date | Subject | |
---|---|---|---|
Next Message | Oisin Glynn | 2006-03-02 20:45:01 | [Fwd: Schema Question] |
Previous Message | Andrew Watkins | 2006-03-02 20:41:26 | Linux cluster application |