From: | Harold Falkmeyer <hfalkmeyer(at)gmail(dot)com> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Immediate Shutdowns |
Date: | 2017-06-07 02:56:24 |
Message-ID: | CACcYrisGrexO5SkHL++UVQ3VEgPe5UzGK4nC9R_JCmOuyfFRyg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Greetings,
Are there long-term detriments from executing an immediate shutdown and/or
issuing SIGQUITs to either the parent or any child postmaster? I'm aware
that PostgreSQL, upon next start, performs a WAL replay and performs other
crash recovery steps. Are there certain operations, such as VACUUM
ANALYZEs, CREATE INDEXs, INSERTs, UPDATEs, and/or DELETEs, for example,
that are less easily recovered or less recoverable than other operations?
What might cause an operation, such as a VACUUM ANALYZE, not to exit upon
receiving a SIGTERM. Are there any circumstances when a SIGQUIT could fail
to cause an imminent exit (other than a process in an fundamentally
unreceptive state, such as an uninterruptible sleep).
Thank you in advance,
Harold Falkmeyer
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-07 03:25:04 | Re: Immediate Shutdowns |
Previous Message | Harold Falkmeyer | 2017-06-06 18:43:22 | Re: VACUUM ANALYZE Issues |