Re: Hot Standby query cancellation and Streaming Replication integration - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Hot Standby query cancellation and Streaming Replication integration
Date
Msg-id 407d949e1003011646t48b41b44sc5fc610cacae34b9@mail.gmail.com
Whole thread Raw
In response to Re: Re: Hot Standby query cancellation and Streaming Replication integration  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Re: Hot Standby query cancellation and Streaming Replication integration
List pgsql-hackers
<p>josh, nobody is talking about it because it doesn't make sense. you could only retry if it was the first query in
thetransaction and only if you could prove there were no side-effects outside the database and then you would have no
reasonto think the retry would be any more likely to work. <p>greg<p><blockquote type="cite">On 1 Mar 2010 22:32, "Josh
Berkus"<<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>> wrote:<br /><br /><p><font color="#500050">On
2/28/107:12 PM, Robert Haas wrote:<br />>> However, I'd still like to hear from someone with the requ...</font>
"deadend" as in "too hard to implement"?  Or for some other reason?<br /><br /> It's undeniable that auto-retry would
bebetter from a user's<br /> perspective than a user-visible cancel.  So if it's *reasonable* to<br /> implement, I
thinkwe should be working on it.  I'm also very puzzled as<br /> to why nobody else wants to even discuss it; it's like
somewierd blackout.<br /><font color="#888888"><br /> --Josh Berkus<br /></font><p><font color="#500050"><br />-- <br
/>Sentvia pgsql-hackers mailing list (<a
href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br/>To make changes to your
subs...</font></blockquote>

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: scheduler in core
Next
From: Tom Lane
Date:
Subject: Re: Re: Hot Standby query cancellation and Streaming Replication integration