Re: BUG #13518: CancelRequest lacks statement identifier

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kevin Grittner <kgrittn(at)ymail(dot)com>, "niallfr(at)btinternet(dot)com" <niallfr(at)btinternet(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #13518: CancelRequest lacks statement identifier
Date: 2015-07-28 20:06:13
Message-ID: 20150728200613.GJ4726@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2015-07-28 15:57:26 -0400, Tom Lane wrote:
> The bigger picture though is that what you're suggesting would require
> that a whole new connection be made in order to issue a Cancel. That's
> kind of an expensive solution ...

On the other hand that'd allow us to do authentication, ssl, etc for
cancel requests. Which would also be kinda nice...

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message bobby.rullo 2015-07-28 20:45:30 BUG #13524: Not Getting expected Serialization error
Previous Message Tom Lane 2015-07-28 19:57:26 Re: BUG #13518: CancelRequest lacks statement identifier