On Fri, Sep 21, 2012 at 9:38 AM, Bartosz Dmytrak <bdmytrak@gmail.com> wrote:
>
>
> 2012/9/19 Tom Browder <tom.browder@gmail.com>
>>
>> I want to upgrade my existing installation and would like to ensure
>> the db is not modified until I get the new installation running.
>>
>> Is there any way to restart into a single user mode so that a
>> pg_dumpall works as the superuser? Or am I limited to a stop, fiddle
>> with pg_hba.conf, restart, pg_dumpall, etc.?
>>
>> Thanks,
>>
>> -To
>> m
>>
>
> Hi
> according to doc
> (http://www.postgresql.org/docs/9.2/static/auth-pg-hba-conf.html):
> "If you edit the file on an active system, you will need to signal the
> postmaster (using pg_ctl reload or kill -HUP)"
>
> so, again according to doc
> (http://www.postgresql.org/docs/9.2/static/app-pg-ctl.html):
> "reload mode simply sends the postgres process a SIGHUP signal, causing it
> to reread its configuration files (postgresql.conf, pg_hba.conf, etc.). This
> allows changing of configuration-file options that do not require a complete
> restart to take effect."
>
> One advise:
> 1. change pg_hba.conf;
> 2. kill all user sessions (or kindly ask them to disconect);
> 3. reload configuration;
> 4. You're ready to updgrade.
Thanks, Bartek, that's what I was afraid of.
It would be nice to have such a postgres mode though for just such
things as an upgrade.
Best,
-Thanks
