Re: Re: Hot Standby query cancellation and Streaming Replication integration

* Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> [100301 20:04]:
> Greg Stark <stark(at)mit(dot)edu> writes:
> > josh, nobody is talking about it because it doesn't make sense. you could
> > only retry if it was the first query in the transaction and only if you
> > could prove there were no side-effects outside the database and then you
> > would have no reason to think the retry would be any more likely to work.
>
> But it's hot standby, so there are no data-modifying transactions.
> Volatile functions could be a problem, though. A bigger problem is
> we might have already shipped partial query results to the client.

But, since we know its a slave and that the reason the query was
cancelled was because it's got a backlog of updates to apply, it's very
likely that the data that the earlier parts of the transaction would be
different...

And then you have no idea if just blindly replaying all statements of
the transaction successively is a good idea...

a.

--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.