On Wed, Oct 27, 2010 at 6:44 PM, Jaime Casanova wrote:
> On Wed, Oct 27, 2010 at 6:18 PM, Daniel Farina wrote:
>>
>> As a result, "aborting startup due to startup process failure" is seen
>> in the log, but not the messages seen in
>> xlog.c:readRecoveryCommandFile that triggered the failure.
>>
On Wed, Oct 27, 2010 at 6:18 PM, Daniel Farina wrote:
>
> As a result, "aborting startup due to startup process failure" is seen
> in the log, but not the messages seen in
> xlog.c:readRecoveryCommandFile that triggered the failure.
>
can you explain what steps you did to reproduce this?
--
Jai
Hello list,
I just encountered an interesting undesirable behavior in Postgres
9.0's error reporting dealing with (trivially) malformed
recovery.conf, as might be the case when setting up hot standby. In
this case, there were some missing fields, and they were checked as
they are supposed to be in
