Skip site navigation (1) Skip section navigation (2)

Re: [PATCHES] Automatic transactions in psql

From: Thomas Lockhart <lockhart(at)fourpalms(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)turnstep(dot)com>,Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Automatic transactions in psql
Date: 2002-02-22 15:21:51
Message-ID: 3C76620F.C73CBE11@fourpalms.org (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
...
> > Secondly, it adds a "begin transaction" option that, when
> > enabled, ensures that you are always inside a transaction
> > while in psql, so you can always rollback. It does this
> > by issuing a BEGIN at the appropriate times. This patch
> > (if ever accepted) conflicts a bit with LO_RTANSACTION:
> > psql now *does* have a way to know if it is in a
> > transaction or not, so that part may need to get rewritten.

This part of the feature (corresponding to the Ingres "autocommit = off"
feature) should be implemented in the backend rather than in psql. I've
had a moderate interest in doing this but haven't gotten to it; if
someone wants to pick it up I'm sure it would be well received...

                      - Thomas

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-02-22 15:39:25
Subject: Re: problem with restore of functions
Previous:From: Oleg BartunovDate: 2002-02-22 15:20:14
Subject: Re: problem with restore of functions

pgsql-patches by date

Next:From: Bruce MomjianDate: 2002-02-22 16:09:48
Subject: Re: [PATCHES] Automatic transactions in psql
Previous:From: Fernando NasserDate: 2002-02-22 14:44:13
Subject: Fix command completion for CREATE TABEL ... AS

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group