From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Change of pg_ctl's default shutdown method |
Date: | 2015-03-20 22:19:37 |
Message-ID: | 20150320221937.GV6317@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
We originally chose "smart" as the default pg_ctl shutdown method
because it was the least disruptive, but experience has shown that it is
too polite, so the current default is inconvenient.
We have discussed changing the default shutdown mode to "fast", and 9.5
might be the release where we do that. The attached patch accomplishes
this.
I have not re-ordered the shutdown method options because I am trying to
keep the list logical, from least to most severe, so "smart" is still
listed first. It is odd that the default is the middle option, but I
don't see any other idea on improving that. How do we handle other
cases where the default is in the middle of a range of values?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
Attachment | Content-Type | Size |
---|---|---|
pg_ctl.diff | text/x-diff | 3.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2015-03-20 22:27:55 | Re: GIN code managing entry insertion not able to differentiate fresh and old indexes |
Previous Message | Bruce Momjian | 2015-03-20 21:17:40 | Re: vacuumdb: Help text for --analyze-only. |