From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot Standby conflict resolution handling |
Date: | 2012-12-04 13:24:53 |
Message-ID: | CABOikdM6=ZYsJCQDAt8hN63n3LYFCASdYsU-qW16k03asxu5Ag@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 4, 2012 at 6:01 PM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>wrote:
>
>
> Thanks Andres. I also read the original thread and I now understand why we
> are using FATAL here, at least until we have a better solution. Obviously
> the connection reset is no good either because as someone commented in the
> original discussion, I thought that I'm seeing a server crash while it was
> not.
>
>
How about attached comment to be added at the appropriate place ? I've
extracted this mostly from Tom's explanation in the original thread.
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
Attachment | Content-Type | Size |
---|---|---|
clarify-fatal-error-in-conflict-resolve.patch | application/octet-stream | 1.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2012-12-04 13:26:32 | Re: Bug in buildfarm client |
Previous Message | Andres Freund | 2012-12-04 13:16:23 | Re: PageIsAllVisible()'s trustworthiness in Hot Standby |