On May 4, 2010, at 3:48 PM, Gurjeet Singh wrote:
There are quite a few GUC parameters that need restart. Is there a way we can
avoid some of them needing restart? I am specifically looking at archive_mode
and the new wal_level.
For archive_mode you should check the archives; where was
Jim Nasby wrote:
For archive_mode you should check the archives; where was discussion on exactly
why we can only enable archiving on restart. That GUC was added specifically so
that archive_command didn't require a restart
I linked the most relevant bits from the archives into
There are quite a few GUC parameters that need restart. Is there a way we
can avoid some of them needing restart? I am specifically looking at
archive_mode and the new wal_level.
From my limited understanding, these parameters need restart because in a
running cluster we cannot safely change
Gurjeet Singh singh.gurj...@gmail.com wrote:
There are quite a few GUC parameters that need restart. Is there a
way we can avoid some of them needing restart? I am specifically
looking at archive_mode and the new wal_level.
I'll second this on a don't know if it's practicable, but it would
