On Wed, Oct 26, 2011 at 6:09 PM, patrick keshishian <pkeshish@xxxxxxxxx> wrote: > On Wed, Oct 26, 2011 at 4:49 PM, William E. Moreno A. > <wmoreno3@xxxxxxxxx> wrote: >> Solution: http://archives.postgresql.org/pgsql-general/2007-12/msg01339.php >> Solution: Message-id: <476D6DE1.4050600@xxxxxxxxx> >> <text/plain> >> >> Problem: FATAL: the database system is starting up >> >> Solved: change postgresql_flags in /etc/rc.conf to: postgresql_flags="-s -m fast" or postgresql_flags="-s -m smart" > > interesting enough, got bit by this recently. Our set up does not have > a "-w" option. During upgrades we "cycle" our PostgreSQL daemon. We > had to change the "pg_ctl stop" command to "-mimmediate" because > during upgrades we would find that someone had an abandoned psql shell > running for days and that would halt our upgrade script. > > Adding "-m immediate" for shutdown seemed like a logical choice to get > around this sort of a "procedural" issue(s). didn't -m fast work? -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
