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

Re: postgresql.conf archive_command example

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, Cédric Villemain <cedric(dot)villemain(dot)debian(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgresql.conf archive_command example
Date: 2011-09-01 11:06:09
Message-ID: CA+Tgmobjv9BsJaMWZKyOb0gpaR99cBj4m6rU32_K9VAH+DPikg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
2011/9/1 Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
>> Well, we could make initdb patch it up, but that might seem excessive.
>
> I sometime wonder if archive_mode shouldn't default to "on" with the
> archive_command set to either '/bin/true' or 'rem' for windows.
>
> That allows to install proper archiving without restart, but the
> tradeoff is of course that you need to restart to enable some
> optimisation cases by turning archive_mode off.

Seems like it would be better to fix archive_mode so that it can be
changed without a restart.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2011-09-01 11:22:43
Subject: pgsql: Remove "fmgr.h" include in cube contrib --- caused crash on aGe
Previous:From: Heikki LinnakangasDate: 2011-09-01 09:37:42
Subject: Re: WIP: Fast GiST index build

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