Re: GUCs that need restart

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Gurjeet Singh <singh(dot)gurjeet(at)gmail(dot)com>
Cc: PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GUCs that need restart
Date: 2010-05-17 18:21:38
Message-ID: 21A03C80-D475-429B-80C6-F38CD47B5732@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 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.
--
Jim C. Nasby, Database Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-05-17 18:31:57 Re: message style for errcontext
Previous Message Peter Eisentraut 2010-05-17 18:20:21 message style for errcontext