Re: Linux cluster application

From: Douglas McNaught <doug(at)mcnaught(dot)org>
To: Andrew Watkins <andrew(at)cse(dot)msstate(dot)edu>
Cc: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Linux cluster application
Date: 2006-03-03 14:31:41
Message-ID: 87d5h3lhv6.fsf@suzuka.mcnaught.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Andrew Watkins <andrew(at)cse(dot)msstate(dot)edu> writes:

> Thanks. I suppose my question is less about the mechanisms for
> actually starting the servers and more about where to install the
> servers, where they should be running, etc. For example, if I'm using
> a shared file system across each node in the cluster and postgres has
> been installed in, say, /home/user/pgres, and initdb has initialized
> the database on, say, /home/user/pgres/data, then it would seem like
> there would end up being conflicts in file names when trying to launch
> a local server on each node. On the other hand, if there is disk space
> local to each node, then running the servers there would not allow for
> the assessing of the impact on a parallel file system.

You will definitely have to run initdb, and start Postgres, with a
unique data directory for each machine (maybe named after the host?)
-- having more than one server process trying to use a single
directory will break everything.

-Doug

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-03-03 14:33:49 Re: extended index info
Previous Message Sascha Nepper 2006-03-03 14:20:00 Re: ERROR: column "datpath" does not exist