Comment 6 for bug 138793

Martin,

Having just run this again, I can report that the conf
files are deposited in the data directory when you run
initdb.

Also, for the postgresql server to start, I must copy
server.crt, server.key and root.crt from
/var/lib/postgresql/8.1/main to the data directory,
and change the owner of those files to postgres.
Otherwise, no go.

> dpkg -l 'postgres*' | grep ^ii

I get postgresql-8.1, postgresql-client-8.1,
postgresql-common, and postgresql-client-common. The
first two are version 8.1.9-0ubuntu0.6.06.

> lsb_release -d

Ubuntu 6.06.1 LTS

> It does not happen on Ubuntu
> Feisty/Gutsy and Debian Etch/unstable.

For a database sever, I think most real database
administrators would choose a long term support
version over unstable!

Rick

--- Martin Pitt <email address hidden> wrote:

> Hi Rick,
>
> Rick Graves [2007-10-24 3:34 -0000]:
> > Part of my problem was the conf files were not
> just in
> > /etc/postgresql, but in /etc/postgresql/8.1/main
>
> This is because we support multiple versions in
> parallel, and also
> multiple clusters (instances) of one version in
> parallel. Please see
> /usr/share/doc/postgresql-common/README.gz.
>
> > deep, I found the conf files in the data directory
> > instead).
>
> This would be one major part of the bug. It does not
> happen on Ubuntu
> Feisty/Gutsy and Debian Etch/unstable. Please give
> me the output of
>
> dpkg -l 'postgres*' | grep ^ii
> lsb_release -d
>
> Thanks,
>
> Martin
>
> --
> no warning about decoy conf files
> https://bugs.launchpad.net/bugs/138793
> You received this bug notification because you are a
> direct subscriber
> of the bug.
>