pgsql: Fix (some of the) breakage introduced into query-cancel
От | tgl@postgresql.org (Tom Lane) |
---|---|
Тема | pgsql: Fix (some of the) breakage introduced into query-cancel |
Дата | |
Msg-id | 20100107162958.EC90A7541B9@cvs.postgresql.org обсуждение исходный текст |
Ответы |
Re: pgsql: Fix (some of the) breakage introduced into
query-cancel
Re: pgsql: Fix (some of the) breakage introduced into query-cancel |
Список | pgsql-committers |
Log Message: ----------- 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. Instead of that, undo the original optimizations that threw away QueryCancelPending anytime we were starting or finishing a command read, and instead discard the cancel request within ProcessInterrupts if we find that there is no HS reason for forcing a cancel and we are DoingCommandRead. In passing, may I once again condemn the practice of changing the code and not fixing the adjacent comment that you just turned into a lie? Modified Files: -------------- pgsql/src/backend/tcop: postgres.c (r1.580 -> r1.581) (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/tcop/postgres.c?r1=1.580&r2=1.581)
В списке pgsql-committers по дате отправления: