Re: Postgres 10.7 Systemd Startup Issue - Mailing list pgsql-general

From Tom Lane
Subject Re: Postgres 10.7 Systemd Startup Issue
Date
Msg-id 5771.1559866748@sss.pgh.pa.us
Whole thread Raw
In response to Re: Postgres 10.7 Systemd Startup Issue  (Francisco Olarte <folarte@peoplecall.com>)
Responses Re: Postgres 10.7 Systemd Startup Issue
Re: Postgres 10.7 Systemd Startup Issue
List pgsql-general
Francisco Olarte <folarte@peoplecall.com> writes:
> On Thu, Jun 6, 2019 at 6:57 PM Kelly, Kevin <Kevin.Kelly@sig.com> wrote:
>> We’re attempting to launch postgres via systemd and noticing that when invoking via systemctl start postgres.service
theprompt never returns. If we switch to another tty and check the status it shows as: 
>> Active: activating (start) since Thu 2019-06-06 09:36:32 EDT; 12min ago
>> If we change the type from notify to forking we see the same behavior. The instance seems to be up and running just
fine,we just never see the active (running) status as we have come to expect. 

> Are you sure you have the postgres.service correctly configured? ( or
> you could post the ExecStart/Type config, or the whole service file ).

> The type tells systemd how to know the service has finished starting
> and is running, notify means it does systemd integration via socket,
> with IIRC postgres does not.

I might be confusing this with some other issue, but I think PG does
support systemd notification if you build it with the --with-systemd
configuration option.  This is recommended if you're using systemd
to launch PG, because systemd's other options for figuring out the
service state work substantially less well.

            regards, tom lane



pgsql-general by date:

Previous
From: Jan Bilek
Date:
Subject: RE: Requirement PA-DSS 1.1.4
Next
From: Christopher Browne
Date:
Subject: Re: Postgres 10.7 Systemd Startup Issue