Tom Lane writes:

> * Backend's ReadyForQuery message (Z message) should carry an indication
> of current transaction status (idle/in transaction/in aborted transaction)
> so that frontend need not guess at state.  Perhaps also indicate
> autocommit status.

If we do this, could we get rid of the messy autocommit GUC option and
handle autocommit in the client?  Before sending a command, the client
could check the transaction status and automatically choose to start a new
transaction.  That way we could get rid of the current mess that every
client needs to send a SET autocommit command before it can safely do

Peter Eisentraut   [EMAIL PROTECTED]

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to