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

Re: Vote totals for SET in aborted transaction

From: Jan Wieck <janwieck(at)yahoo(dot)com>
To: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
Cc: Jan Wieck <janwieck(at)yahoo(dot)com>,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>,Vince Vielhaber <vev(at)michvhf(dot)com>,Mike Mascari <mascarm(at)mascari(dot)com>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Vote totals for SET in aborted transaction
Date: 2002-04-26 13:33:25
Message-ID: 200204261333.g3QDXPS08896@saturn.janwieck.net (view raw or flat)
Thread:
Lists: pgsql-hackers
Marc G. Fournier wrote:
> On Fri, 26 Apr 2002, Jan Wieck wrote:
>
> > Bruce Momjian wrote:
> > > Marc G. Fournier wrote:
> > > > On Thu, 25 Apr 2002, Bruce Momjian wrote:
> > > >
> > > > >
> > > > > Marc is suggesting we may want to match Oracle somehow.
> > > > >
> > > > > I just want to have our SET work on a sane manner.
> > > >
> > > > Myself, I wonder why Oracle went the route they went ... does anyone have
> > > > access to a Sybase / Informix system, to confirm how they do it?  Is
> > > > Oracle the 'odd man out', or are we going to be that?  *Adding* something
> > > > (ie. DROP TABLE rollbacks) that nobody appears to have is one thing ...
> > > > but changing the behaviour is a totally different ...
> > >
> > > Yes, let's find out what the others do.  I don't see DROP TABLE
> > > rollbacking as totally different.  How is it different from SET?
> >
> >     Man,  you  should know that our transactions are truly all or
> >     nothing.  If you discard a transaction, the stamps  xmin  and
> >     xmax are ignored.  This is a fundamental feature of Postgres,
> >     and if you're half through a utility command when  you  ERROR
> >     out,  it  guarantees consistency of the catalog.  And now you
> >     want us to violate this concept for compatibility to Oracle's
> >     misbehaviour? No, thanks!
>
> How does SET relate to xmin/xmax? :)
>

    SET does not. But Bruce said he doesn't see DROP TABLE beeing
    totally different. That is related to  xmin/xmax,  isn't  it?
    What  I  pointed  out  (or  wanted  to point out) is, that we
    cannot ignore rollback for catalog changes like DROP TABLE.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #



In response to

Responses

pgsql-hackers by date

Next:From: Doug McNaughtDate: 2002-04-26 13:38:55
Subject: Re: PSQL \x \l command issues
Previous:From: Marc G. FournierDate: 2002-04-26 13:24:12
Subject: Re: Vote totals for SET in aborted transaction

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