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

Re: autocommit off mode, how does it work?

From: Dave Cramer <dave(at)fastcrypt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 'pgsql-hackers' <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: autocommit off mode, how does it work?
Date: 2003-02-26 11:58:01
Message-ID: 1046260680.30607.15.camel@inspiron.cramers (view raw or flat)
Thread:
Lists: pgsql-hackers
Sorry for the noise, my instance of postgres was broken.

Dave
On Wed, 2003-02-26 at 02:19, Dave Cramer wrote:
> what cvs version are you working with?
> 
> Dave
> On Wed, 2003-02-26 at 01:11, Tom Lane wrote:
> > Dave Cramer <dave(at)fastcrypt(dot)com> writes:
> > > Can someone point me to the documentation for the new autocommit mode
> > > behaviour, I must be doing something wrong
> > 
> > Must be :-(.  I repeated your example as best I could, and it behaved
> > as expected.
> > 
> > << session 1 >>
> > 
> > regression=# set autocommit=off;
> > SET
> > regression=# begin;
> > BEGIN
> > regression=# create table foo (f1 int);
> > CREATE TABLE
> > regression=# insert into foo values (1);
> > INSERT 933631 1
> > regression=# end;
> > COMMIT
> > regression=#
> > 
> > << session 2 >>
> > 
> > regression=# \d foo
> >       Table "public.foo"
> >  Column |  Type   | Modifiers
> > --------+---------+-----------
> >  f1     | integer |
> > 
> > regression=# select * from foo;
> >  f1
> > ----
> >   1
> > (1 row)
> > 
> > 
> > 			regards, tom lane
-- 
Dave Cramer <dave(at)fastcrypt(dot)com>
Cramer Consulting


In response to

pgsql-hackers by date

Next:From: Andrew SullivanDate: 2003-02-26 12:00:40
Subject: Re: Index File growing big.
Previous:From: Hannu KrosingDate: 2003-02-26 11:10:46
Subject: Re: numeric datataypes as seperate library

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