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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Jaime Casanova <jaime(at)2ndquadrant(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Date: 2011-03-08 03:04:26
Message-ID: 22191.1299553466@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Fujii Masao <masao(dot)fujii(at)gmail(dot)com> writes:
> What about the attached patch?

> + 						ereport(LOG,
> + 								(errmsg("Recovery has paused. Execute pg_xlog_replay_resume() to continue.")));

This isn't even close to following our message style guidelines ...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Fujii MasaoDate: 2011-03-08 03:04:34
Subject: Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Previous:From: davegDate: 2011-03-08 02:51:28
Subject: Re: PD_ALL_VISIBLE flag was incorrectly set happend during repeatable vacuum

pgsql-committers by date

Next:From: Fujii MasaoDate: 2011-03-08 03:04:34
Subject: Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,
Previous:From: Fujii MasaoDate: 2011-03-08 02:36:09
Subject: Re: pgsql: Basic Recovery Control functions for use in Hot Standby. Pause,

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