[Pkg-postgresql-public] Bug#710093: postgresql: not started automatically after installation in chroot

[Andreas Beckmann]

Control: tags -1 - moreinfo
Control: severity -1 serious

Hi Christoph,

On 2013-05-30 06:00, Christoph Berg wrote:
> Re: Andreas Beckmann 2013-05-28 <20130528082018.7493.49330.reportbug at cake.ae.cs.uni-frankfurt.de>
>> I'm experimenting with db support for piuparts tests and therefore
>> postgresql needs to be installed and started in the test chroots.
> 
> Fwiw, which services/packages come with out-of-the-box usable
> PostgreSQL support? For me, dbconfig-common sort of never works...

For piuparts, dbconfig-common seems to work for most packages.
DEBIAN_FRONTEND=noninteractive, all defaults. No clue if the services
are working, but their package installation passes (and usually fails if
the db server is not available). :-)

> Can you check /var/log/postgresql/ if there's any error messages for
> the first startup?

there is only an empty /var/log/postgresql/postgresql-9.1-main.log

I can reproduce this manually with pbuilder in the minimal chroot
created by piuparts. But not in my regular pbuilder chroot. (postgresql
is running there if permitted by policy-rc.d).
I can "fix" this in the piuparts chroot if I install devscripts first
and postgresql afterwards - now the daemon is running.


Andreas

PS: I noticed that pg uses ports 5433, 5434, ... if 5432 is not
available during installation - is there a way (preferrably via
preseeding) that forces it to use 5432 (as that is expected by many
other packages) and just fail if that is not available?