Skip site navigation (1) Skip section navigation (2)

Re: Enabling archive_mode without restart

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Enabling archive_mode without restart
Date: 2008-10-31 16:34:50
Message-ID: 490B33AA.10704@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Joshua D. Drake wrote:
> Kevin Grittner wrote:
>>>>> "Joshua D. Drake" <jd(at)commandprompt(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2008-10-31 16:37:01
Subject: Re: Enabling archive_mode without restart
Previous:From: Hannu KrosingDate: 2008-10-31 16:31:33
Subject: Re: SQL/MED compatible connection manager

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group