Re: pg_cancel_backend() doesn't abort a transaction

With that said, it looks like the commentary for StatementCancelHandler() is not accurate.

> On 10. Jun 2020, at 17:09, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wednesday, June 10, 2020, Andrei Zhidenkov <andrei(dot)zhidenkov(at)n26(dot)com <mailto:andrei(dot)zhidenkov(at)n26(dot)com>> wrote:
>
> The result is that status = 'y' WHERE foo = 1 , so Session 1 committed the transaction successfully. I am missing something or the commentary is vague?
>
> P.S. It's not clear from the documentation whether pg_cancel_backend() aborts transaction or not
>
> User-facing docs seem reasonably clear: “ Cancel a backend's current query. “
>
> It makes it so that current query fails, nothing more. If that query is part of a transaction it will typically cause subsequent statements to fail since the transaction is in an aborted state. However, if the transaction can cope with that statement failing, as your example does using savepoints, the transaction can continue onto normal completion.
>
> From what you say the source code comments seem to be written for the common case, but “query-cancel” should/does impact just a single query and does not target the transaction directly.
>
> It does not seem desirable that the containing transaction be affected directly nor surely does changing the behavior make sense at this point.
>
> David J.
>