Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> On Thu, 2010-01-07 at 16:29 +0000, Tom Lane wrote:
>> Fix (some of the) breakage introduced into query-cancel processing by HS.

>> 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.

> ...That was not introduced by HS.

Yes it was; or at least it was in your HS commit:

http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c.diff?r1=1.578;r2=1.579

			regards, tom lane

In response to

• Re: pgsql: Fix (some of the) breakage introduced into query-cancel at 2010-01-07 20:21:27 from Simon Riggs

Responses

• Re: pgsql: Fix (some of the) breakage introduced into query-cancel at 2010-01-07 20:46:49 from Simon Riggs

pgsql-committers by date

Next:	From: Robert Haas	Date: 2010-01-07 20:39:45
	Subject: pgsql: Document why we copy reloptions into CacheMemoryContext
Previous:	From: Simon Riggs	Date: 2010-01-07 20:21:27
	Subject: Re: pgsql: Fix (some of the) breakage introduced into query-cancel