> > DEBUG: InitPostgres
> > DEBUG: StartTransactionCommand
> > DEBUG: query: select getdatabaseencoding()
> > DEBUG: ProcessQuery
> > DEBUG: CommitTransactionCommand
> > DEBUG: StartTransactionCommand
> > DEBUG: query: RESET ALL
> > DEBUG: ProcessUtility: RESET ALL
> > DEBUG: CommitTransactionCommand
> > DEBUG: StartTransactionCommand
> > DEBUG: query: BEGIN;ROLLBACK;
> > DEBUG: ProcessUtility: BEGIN;ROLLBACK;
> > DEBUG: CommitTransactionCommand
> > DEBUG: StartTransactionCommand
> > DEBUG: ProcessUtility: BEGIN;ROLLBACK;
> > DEBUG: CommitTransactionCommand
> > DEBUG: pq_recvbuf: unexpected EOF on client connection
> >
>
> And this is the wrong order of things. The BEGIN;ROLLBACK; has to be
> done first, otherwise if the connection was left in an aborted open
> transaction by the previous script, the other two actions will fail.
Surely PHP can be modified so as to use the new 3.0 protocol feature to
detect whether it's in a transaction or not, so as to avoid unnecssary
querying?
Chris
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
