Re: Enabling archive_mode without restart

Joshua D. Drake wrote:
> Kevin Grittner wrote:
>>>>> "Joshua D. Drake" <jd@commandprompt.com> wrote: 
>>> It certainly makes more sense to do this:
> 
>> archive_mode = off
>> archive_command = '/archive/command/used/during/snapshot/backups'
>>  
>> I could live with diddling the command to control archiving.
>>  
>> It doesn't log anything extra when archive_mode is on?
> 
> Depends on your logging level. I don't know that there is noticeable 
> difference between the two in terms of performance. That said, it is 
> still silly that we have to handle it in such a hacky way. Frankly, it 
> should be a catalog reloption of some sort... "ALTER CATALOG (which 
> doesn't exist) archive_mode TO off" but I digress.

archive_mode = on disables the optimization to skip WAL-logging when 
loading into a new table that was created in the same transaction. 
That's the case that Simon described in the mail that started this thread.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com