On Thu, May 7, 2015 at 10:17:18AM -0400, Andrew Dunstan wrote:
>
> On 05/07/2015 09:58 AM, Bruce Momjian wrote:
>
> >
> >Frankly, I am not sure how they are starting the server as the
> >/etc/init.d startup files don't handle multiple clusters well, and I
> >have never seen instructions on how multi-cluster users are supposed to
> >set things up. I assume they are copying the existing init.d file with
> >a new name and modifying PGDATA and maybe the port number, then doing
> >'service ... start' or something like that. I doubt we want initdb to
> >recommend that.
> >
>
>
> Then you haven't been paying attention, and no, that's not the right
> way to do it. The PGDG RPMs, for example, support multi-tenancy very
> easily, both for systems that use init scripts and those using
> systemd. I have blogged about how to do this here:
<http://web.archive.org/web/20111127175231/http://people.planetpostgresql.org/andrew/index.php?/archives/233-Multi-tenancy-under-systemd.html>
> and here
<http://web.archive.org/web/20111221072621/http://people.planetpostgresql.org/andrew/index.php?/archives/134-Multi-tenancy-done-right.html>
Uh, those posts are 5 years old and you had to get them from the Wayback
machine --- I think you made my point. :-)
> But in any case, it's largely irrelevant, ISTM. Anybody who actually
> needs that message from initdb should almost be using pg_ctl instead
> of calling postgres direct.
Agreed.
-- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB
http://enterprisedb.com
+ Everyone has their own god. +