Type: | bool |
Default: | on |
Context: | sighup |
Restart: | false |
When set to on, which is the default, PostgreSQL will automatically reinitialize after a backend crash. Leaving this value set to on is normally the best way to maximize the availability of the database. However, in some circumstances, such as when PostgreSQL is being invoked by clusterware, it may be useful to disable the restart so that the clusterware can gain control and take any actions it deems appropriate.
This parameter can only be set in the postgresql.conf file or on the server command line.
Recommendations
… unless deliberately running postgres in “ephemeral mode”
On StackOverflow
On pgsql-hackers
- Fix background workers not restarting with restart_after_crash = on
- Re: Logical replication launcher did not automatically restart when got SIGKILL
- Re: Non-reproducible AIO failure
- Re: Assertion failure when autovacuum drops orphan temp indexes.
- Re: processes stuck in shutdown following OOM/recovery