Re: (re)start in our init scripts seems broken - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: (re)start in our init scripts seems broken
Date
Msg-id CAB7nPqTunrVKFTDh46QDn0Z46KAMyCwbDtw6mP5696W5tonwcQ@mail.gmail.com
Whole thread Raw
In response to (re)start in our init scripts seems broken  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: (re)start in our init scripts seems broken
List pgsql-hackers
On Wed, Jul 20, 2016 at 11:41 AM, Tomas Vondra
<tomas.vondra@2ndquadrant.com> wrote:
> Is there a reason why it's coded like this? I think we should use the pg_ctl
> instead or (at the very least) check the postmaster return code. Also,
> perhaps we should add an explicit timeout, higher than 60 seconds.

c8196c87 is one reason. Honestly, I have always found that using
pg_ctl start -w is more robust in such scripts, and it avoids
maintaining sanity checks that are duplicates of the ones in pg_ctl
after the postmaster has started. So +1 for using that. Passing the
PG_OOM_* flags is not an issue either.
-- 
Michael



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: plperl loading files
Next
From: Andres Freund
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Avoid extra locks in GetSnapshotData if old_snapshot_threshold <