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

Re: [COMMITTERS] pgsql: Add restart_after_crash GUC.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Robert Haas <rhaas(at)postgresql(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Add restart_after_crash GUC.
Date: 2010-07-27 16:07:00
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
On Tue, Jul 27, 2010 at 2:33 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Tue, Jul 20, 2010 at 9:47 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
>> Log Message:
>> -----------
>> Add restart_after_crash GUC.
> In postgresql.conf.sample, on/off is used as a boolean value.
> But true/false is used for exit_on_error and restart_after_crash.
> Sorry, I had overlooked that inconsistency when reviewing the
> original patch. I attached the bug-fix patch.

Good catch, thanks.  Committed.

Robert Haas
The Enterprise Postgres Company

In response to

pgsql-hackers by date

Next:From: Dimitri FontaineDate: 2010-07-27 16:58:03
Subject: Re: Synchronous replication
Previous:From: Joshua TolleyDate: 2010-07-27 14:57:03
Subject: Re: Synchronous replication

pgsql-committers by date

Next:From: Peter EisentrautDate: 2010-07-27 18:54:29
Subject: pgsql: Spelling fix
Previous:From: Robert HaasDate: 2010-07-27 16:06:53
Subject: pgsql: In postgresql.conf.sample, use on/off rather than true/false.

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