On Sun, Jan 10, 2010 at 07:52:25PM -0800, David Fetter wrote:
> - Fix (some of the) breakage introduced into query-cancel processing
> by Hot Standby. It is absolutely not okay to throw an
> ereport(ERROR) in any random place in the code just because
> DoingCommandRead is set; interrupting, say, OpenSSL in the midst of
> its activities is guaranteed to result in heartache. Instead of
> that, undo the original optimizations that threw away
> QueryCancelPending anytime we were starting or finishing a command
> read, and instead discard the cancel request within
> ProcessInterrupts if we find that there is no Hiroshi Saito reason
Oops. Hoist by my own petard. That should read, "...there is no Hot
Standby reason."
Cheers,
David.
--
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david.fetter@gmail.com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate