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

Re: disable archiving

From: Paul van den Bogaard <Paul(dot)Vandenbogaard(at)Sun(dot)COM>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: disable archiving
Date: 2007-07-23 17:42:06
Message-ID: BD28A71D-6AB4-4BD8-9458-AEEDE94F3120@Sun.COM (view raw, whole thread or download thread mbox)
Lists: pgsql-performance

thanks for the quick reply. Just to make sure: I do not set this  
command. This results in the database cycling through a finite set  
(hopefully small) set of WAL files. So old WAL files are reused once  
the engine thinks this can be done.


On 23-jul-2007, at 19:34, Alvaro Herrera wrote:

> Paul van den Bogaard wrote:
>> the manual somewhere states "... if archiving is enabled..." To me  
>> this
>> implies that archiving can be disabled. However I cannot find the  
>> parameter
>> to use to get this result.
> Archiving is disabled by not setting archive_command.
> -- 
> Alvaro Herrera                                http:// 
> The PostgreSQL Company - Command Prompt, Inc.

Paul van den Bogaard                                
CIE -- Collaboration and ISV Engineering, Opensource Engineering group

Sun Microsystems, Inc                              phone:        +31  
334 515 918
Saturnus 1                                                  
extentsion: x (70)15918
3824 ME Amersfoort                                 mobile:       +31  
651 913 354
The Netherlands                                         
fax:            +31 334 515 001

In response to

pgsql-performance by date

Next:From: Simon RiggsDate: 2007-07-23 17:50:53
Subject: Re: User concurrency thresholding: where do I look?
Previous:From: Arjen van der MeijdenDate: 2007-07-23 17:39:10
Subject: Re: disable archiving

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