Re: Recovery conflict message lost in user session for 9.3

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Recovery conflict message lost in user session for 9.3
Date: 2015-11-26 21:33:39
Message-ID: 56577AB3.4060506@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 27/11/15 05:14, Tom Lane wrote:
>> bench=# fetch hcur;
>> server closed the connection unexpectedly
>> This probably means the server terminated abnormally
>> before or while processing the request.
>> The connection to the server was lost. Attempting reset: Succeeded.
>
>> Now in the standby log I see:
>> FATAL: terminating connection due to conflict with recovery
>> DETAIL: User query might have needed to see row versions that must be
>> removed.
>> HINT: In a moment you should be able to reconnect to the database and
>> repeat your command.
>
>> However this is not transmitted to the standby user's session, so
>> leaving an unhelpful message about why the session got killed.
>
> Please check to see if commit db6e8e162 fixes this.
>

It does :-)

regards

Mark

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Feike Steenbergen 2015-11-27 13:21:39 Re: BUG #13785: Postgresql encoding screw-up
Previous Message Tom Lane 2015-11-26 16:14:28 Re: Recovery conflict message lost in user session for 9.3