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

Re: [HACKERS] MVCC works in serialized mode!

From: Theo Kramer <theo(at)flame(dot)co(dot)za>
To: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] MVCC works in serialized mode!
Date: 1998-12-28 14:04:56
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Bruce Momjian wrote:
> > > 7. As I read in Sybase documentation the default
> > >    standard transaction mode is _chained_ - all
> > >    queries before explicit COMMIT/ABORT are run in _single
> > >    transaction_... But we have to use BEGIN/END to get it!
> > >    This was not so bad for system with relation level locks,
> > >    but now only the same row writes block one other and so
> > >    chained mode seems more appropriate...
> > >
> > >    Shouldn't we change default transaction mode now?
> > >    And use option/SET TRANSACTION MODE to switch to
> > >    un-chained mode if one like it?
> >
> > No comments on this?
> > I would like to make BEGIN implicit...
> > Objections?
> Informix requires BEGIN.  Ingres does not, but has 'set autocommit'
> mode, so each SQL statement is its own transaction, like we have now.
> I always felt that if I go in to psql and run a query, I want it
> applied.  I don't want to have to commit every query I type.
> I know I can use SET TRANSACTION MODE to change this.
> What do others think?

As long as we can switch. Interactive applications typically update more
than one objects per transaction.


In response to

pgsql-hackers by date

Next:From: Thomas G. LockhartDate: 1998-12-28 15:39:31
Subject: Re: [HACKERS] MVCC works in serialized mode!
Previous:From: Zeugswetter Andreas IZ5Date: 1998-12-28 09:30:01
Subject: Re: [HACKERS] MVCC works in serialized mode!

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