On Sat, Nov 26, 2016 at 2:52 PM, twoflower <standa.ku...@gmail.com> wrote:
> That makes perfect sense. > > Thank you for a great help, Adrian! > > > > -- > View this message in context: http://postgresql.nabble.com/ > pg-ctl-restart-does-not-terminate-tp5932070p5932095.html > Sent from the PostgreSQL - general mailing list archive at Nabble.com. > > > -- > Sent via pgsql-general mailing list (pgsql-general@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-general > *I feel it important to add one note to this thread. The version of PostgreSQL has not been stated, but it is very * *important to note that the default behavior of pg_ctl has changed between v9.4 and 9.5.https://www.postgresql.org/docs/9.5/static/release-9-5.html <https://www.postgresql.org/docs/9.5/static/release-9-5.html>* - *Change pg_ctl <https://www.postgresql.org/docs/9.5/static/app-pg-ctl.html>'s default shutdown mode from smart to fast (Bruce Momjian)* *This means the default behavior will be to forcibly cancel existing database sessions, not simply wait for them to exit.* *So if the PostgreSQL version is 9.4 or lower, and there are any open connections, the pg_ctl will wait until all connections terminate (either normally or * *are forced off). That "might " explain why pg_ctl never terminated (unless -m fast was also specified). However, if it is version 9.5 or above, then * *-m fast is the default so existing connections will not be a problem. * -- *Melvin Davidson* I reserve the right to fantasize. Whether or not you wish to share my fantasy is entirely up to you.
