Re: incomplete transaction keeps table locked?

From: George Herson <gherson(at)snet(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: incomplete transaction keeps table locked?
Date: 2001-05-23 21:00:12
Message-ID: 3B0C24DC.98079321@snet.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Ok, thanks.

Hopefully upgrading PHP will get auto-rollbacks performed on exit of any
script where i've started a transaction and forgotten to do an explicit
rollback or commit.

george

Tom Lane wrote:
>
> gherson(at)snet(dot)net (George Herson) writes:
> > Are there any circumstances when exiting a PHP web script
> > where you've started a transaction (with Begin Work) but haven't explicitly
> > done a Commit Work or Rollback before it ends will lock you out of
> > a table (until you restart postgresql)?
>
> The symptoms you describe sound like multiple transactions trying to
> update the same row. There is a row-level lock that prevents the later
> ones from completing until the first one commits or aborts.
>
> regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ian Lance Taylor 2001-05-23 21:24:44 Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory
Previous Message Ian Lance Taylor 2001-05-23 20:54:27 Re: Re: ZeroFill(.../pg_xlog/xlogtemp.20148) failed: No such file or directory