From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | adrian(dot)klaver(at)gmail(dot)com, pgsql-general(at)postgresql(dot)org, Torsten Zühlsdorff <foo(at)meisterderspiele(dot)de> |
Subject: | Re: Problem with initdb: creates database which do not exists |
Date: | 2010-10-18 15:15:26 |
Message-ID: | 20101018111526.c5fc47d6.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> writes:
> > On Monday 18 October 2010 7:46:21 am Torsten Z_hlsdorff wrote:
> >> So: any idea why the database is not visible? And how do get rid of the
> >> "non-existing" databases ;)
>
> > My guess is that you have more than one installation of Postgres. The initdb is
> > working on one cluster and your psql is pointing at another.
>
> Yeah. In particular, since I didn't see any server start or stop
> commands in this sequence, it looks like the psql calls are talking to
> some pre-existing server process that's using a pre-existing database
> directory somewhere else.
Unless you tweak settings in /etc/rc.conf, FreeBSD's install of Postgres
will start up talking to the DB in /usr/local/pgsql (if you start it
using FreeBSD's rc system) The port provides the variable postgresql_data
which can be used to change the rc script's behavior.
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Scot Kreienkamp | 2010-10-18 15:28:39 | archiver process problem |
Previous Message | Tom Lane | 2010-10-18 15:11:47 | Re: Problem with initdb: creates database which do not exists |