Re: [INTERFACES] Roadmap for FE/BE protocol redesign

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Date: 2003-03-18 00:40:39
Message-ID: 200303180040.h2I0edq02693@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-interfaces

Peter Eisentraut wrote:
> 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.

What if folks want all their connections autocommit off. Seems it is
best in the server.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruno Wolff III 2003-03-18 01:30:43 Re: who can help me?
Previous Message Bruce Momjian 2003-03-18 00:26:34 Re: ALTER SEQUENCE

Browse pgsql-interfaces by date

  From Date Subject
Next Message Tom Lane 2003-03-18 01:48:41 Re: [INTERFACES] Roadmap for FE/BE protocol redesign
Previous Message Peter Eisentraut 2003-03-18 00:22:55 Re: [INTERFACES] Roadmap for FE/BE protocol redesign