Postgres Pro
Downloads
Home   >   mailing lists

Re: GUCs that need restart - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: GUCs that need restart
Date
Msg-id 21A03C80-D475-429B-80C6-F38CD47B5732@decibel.org
Whole thread Raw
In response to GUCs that need restart  (Gurjeet Singh <singh.gurjeet@gmail.com>)
Responses Re: GUCs that need restart
List pgsql-hackers
Tree view 
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
amspecifically 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@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: including PID or backend ID in relpath of temp rels
Next
From: Jim Nasby
Date:
Subject: Re: Hot Standby tuning for btree_xlog_vacuum()