Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Date: 2011-02-15 00:21:31
Message-ID: 1297729291.1747.18050.camel@ebony
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Wed, 2011-02-09 at 15:22 +0900, Fujii Masao wrote:

> On the second thought, I think it's useful to emit the NOTICE message when
> recovery reaches the pause point, as follows.
>
> NOTICE: Recovery will not complete until pg_xlog_replay_resume() is called.

I'm OK with adding a message, but NOTICE is the wrong level.

My proposal is this message

LOG: Recovery has paused. Execute pg_xlog_replay_resume() to continue.

--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2011-02-15 00:22:56 pgsql: Rearrange extension-related views as per recent discussion.
Previous Message Simon Riggs 2011-02-15 00:10:52 pgsql: Add version-sensitive SQL for psql when constraints NOT VALID

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2011-02-15 00:38:27 Re: .gitignore patch for coverage builds
Previous Message Thom Brown 2011-02-15 00:02:02 Re: tsearch Parser Hacking