From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | pg_upgrade vs. pg_ctl stop -m fast |
Date: | 2017-01-12 15:06:51 |
Message-ID: | 50365cd0-2a9c-83bc-4220-c0c5cb111735@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
In 9.5, the default pg_ctl stop mode was changed from "smart" to "fast".
In pg_upgrade, there is this code:
void
stop_postmaster(bool fast)
{
...
exec_prog(SERVER_STOP_LOG_FILE, NULL, !fast,
"\"%s/pg_ctl\" -w -D \"%s\" -o \"%s\" %s stop",
cluster->bindir, cluster->pgconfig,
cluster->pgopts ? cluster->pgopts : "",
fast ? "-m fast" : "");
...
}
So, when upgrading from 9.5 or later, code that requested a non-fast
shutdown would now always get a fast shutdown.
I think the last line should be changed to something like
fast ? "-m fast" : "-m smart");
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-01-12 15:17:52 | Re: pg_upgrade vs. pg_ctl stop -m fast |
Previous Message | Pavel Stehule | 2017-01-12 15:02:07 | Re: patch: function xmltable |