| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [INTERFACES] Roadmap for FE/BE protocol redesign |
| Date: | 2003-03-18 00:22:55 |
| Message-ID: | Pine.LNX.4.44.0303172059170.1975-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
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
anything.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2003-03-18 00:24:27 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Bruce Momjian | 2003-03-18 00:01:47 | Re: analyze after a database restore? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-03-18 00:40:39 | Re: [INTERFACES] Roadmap for FE/BE protocol redesign |
| Previous Message | Bruce Momjian | 2003-03-17 21:41:48 | Re: Bug #904: Deallocating of prepared statement in ECPG at |