From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | "Brandl\, Wolfgang" <wolfgang(dot)brandl(at)brz(dot)gv(dot)at> |
Cc: | "pgsql-admin\(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: restart_after_crash |
Date: | 2018-09-12 14:43:44 |
Message-ID: | 87lg86vkrj.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Brandl, Wolfgang" <wolfgang(dot)brandl(at)brz(dot)gv(dot)at> writes:
> Hi
> We are testing
> restart_after_crash = on
>
> What is a cras? We killed the Postgres process with -9 SIGSEGV SIGABRT etc.. But never postgres is restarting.
>
> The question arose because of the decision to restart Postgres over systemctl or with the Postgres feature.
>
> But it seems that the Postgres restart is not working or not always working. Or is an additional feature necessary?
It is for a postmaster controlled kill of all backends after a *backend*
crash.
Killing postmaster itself as you are doing does not invoke the feature.
Try choosing any client backend by PID and then do your kill -9 on that
one.
Then expect any other backends to be killed also but the postmaster
still working and then spawning more backend when clients attempt to
connect.
>
> Regards
> Wolfgang
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800
From | Date | Subject | |
---|---|---|---|
Next Message | MirrorX | 2018-09-12 14:47:24 | Re: vacuum and query plans? |
Previous Message | Tom Lane | 2018-09-12 14:28:47 | Re: vacuum and query plans? |