Re: suppress automatic recovery after back crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: suppress automatic recovery after back crash
Date
Msg-id 5035.1277686978@sss.pgh.pa.us
Whole thread Raw
In response to suppress automatic recovery after back crash  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: suppress automatic recovery after back crash  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jun 17, 2010 at 7:25 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Then all you need is a tweak to make the postmaster exit(1) after
>> a crash instead of trying to launch recovery.

> This seems useful to me so here's a patch to implement it.

Hm, is it useful in the absence of the other components of the proposed
feature?

One stylistic gripe:

@@ -80,6 +80,7 @@ enum config_group    COMPAT_OPTIONS,    COMPAT_OPTIONS_PREVIOUS,    COMPAT_OPTIONS_CLIENT,
+    ERROR_HANDLING,    PRESET_OPTIONS,    CUSTOM_OPTIONS,    DEVELOPER_OPTIONS

Please spell that "ERROR_HANDLING_OPTIONS", both for consistency with
the other enum members and to avoid likely conflicts with other uses of
such a generic-looking identifier.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump's checkSeek() seems inadequate
Next
From: Andrew Dunstan
Date:
Subject: Re: pg_dump's checkSeek() seems inadequate