Re: php with postgres

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Jan Wieck" <JanWieck(at)Yahoo(dot)com>, Marcus Börger <marcus(dot)boerger(at)post(dot)rwth-aachen(dot)de>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "ivan" <iv(at)psycho(dot)pl>, "Joe Conway" <mail(at)joeconway(dot)com>, "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: php with postgres
Date: 2003-07-23 01:18:53
Message-ID: 0d9e01c350b8$914f1730$2800a8c0@mars
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2003-07-23 01:33:54 Re: suggestions to improve postgresql suitability for data-mining
Previous Message Christopher Kings-Lynne 2003-07-23 01:17:28 Re: tsearch2 for 7.3.X