Re: Strange result using transactions

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Matthijs Melissen" <melissen(at)phil(dot)uu(dot)nl>, pgsql-general(at)postgresql(dot)org
Subject: Re: Strange result using transactions
Date: 2007-03-27 09:09:06
Message-ID: 2e78013d0703270209j3e5c844cw17edc92f2a5b7ae7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 3/27/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Matthijs Melissen" <melissen(at)phil(dot)uu(dot)nl> writes:
> > I am executing the following queries (id has a unique key):
> > 1) begin;
> > 1) delete from forum where id = 20;
> > 1) insert into forum (id, name) values (20, 'test');
> > 2) delete from forum where id = 20;
> > 1) commit;
>
> > The problem is that process 2 gets the message 'DELETE 0'. I would
> expect
> > him to get the message 'DELETE 1'.
>
> Why do you find that strange? Process 1 hasn't committed its insert yet.
>
>
I think what he is saying that *after* txn 1 commits, txn 2 does not see the
record inserted by txn1. Isn't that a fair point ? I mean txn 2 can see the
DELETE operation of txn 1, but can not see the INSERT operation of the
same transaction.

Thanks,
Pavan

--

EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dmitry Koterov 2007-03-27 10:10:17 Re: Temporarily disable all table indices
Previous Message pol 2007-03-27 07:02:39 to build a vocabulary