Re: Re: PostgreSQL and PHP persistent connections

> > > How is that an improvement? It only changes the case in which you get
> > > a NOTICE from not-in-transaction to in-transaction ...
> >
> > Well, the most common case is that you are not in a transaction.
>
> Why not tracing PQcmdStatus(result) on the persistent
> connection? It allways returns "BEGIN", "COMMIT" or
> "ROLLBACK" for whatever you issued.
>
> Well, it'll not catch the uncommon case that someone might
> issue multiple queries in one statements (semicolon
> separated). But that's IMHO bad practice anyway and the above
> will avoid communication, context switching and eating up of
> XID's until we have silent rollback in 7.2.

It is the multi-command issue that prevented me from suggesting checking
the return status. If they are leaving an open transaction after
disconnecting, they could be doing any crazy thing.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026