commands

Fix bad interaction between NOTIFY processing and V3 extended query

Tom Lane authored 21 years ago

protocol, per report from Igor Shevchenko.  NOTIFY thought it could
do its thing if transaction blockState is TBLOCK_DEFAULT, but in
reality it had better check the low-level transaction state is
TRANS_DEFAULT as well.  Formerly it was not possible to wait for the
client in a state where the first is true and the second is not ...
but now we can have such a state.  Minor cleanup in StartTransaction()
as well.

90b22029

History

90b22029 21 years ago

History

Name	Last commit	Last update
..
Makefile
aggregatecmds.c
alter.c
analyze.c
async.c
cluster.c
comment.c
conversioncmds.c
copy.c
dbcommands.c
define.c
explain.c
functioncmds.c
indexcmds.c
lockcmds.c
opclasscmds.c
operatorcmds.c
portalcmds.c
prepare.c
proclang.c
schemacmds.c
sequence.c
tablecmds.c
trigger.c
typecmds.c
user.c
vacuum.c
vacuumlazy.c
variable.c
view.c