Re: No long-lived transaction, still can't delete tuples

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeffrey Baker <jwbaker(at)acm(dot)org>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: No long-lived transaction, still can't delete tuples
Date: 2002-04-24 22:21:31
Message-ID: 19436.1019686891@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jeffrey Baker <jwbaker(at)acm(dot)org> writes:
> So I believe the transaction is not long-lived. Also, I checked
> with tethereal to make absolutely certain that the commit was
> happening:

> -> 0 5163 6f6d 6d69 7400 Qcommit.
> <- 0 4343 4f4d 4d49 5400 5a CCOMMIT.Z
> -> 0 5162 6567 696e 00 Qbegin.
> <- 0 4342 4547 494e 005a CBEGIN.Z

Isn't that BEGIN opening a new transaction?

Some front-end libraries have a bad habit of issuing a BEGIN instantly
after a commit, rather than waiting for the next command to be issued.
That means your app goes to sleep with an open transaction.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Robert J. Sanford, Jr. 2002-04-24 22:34:59 Re: odd psql behaviour on OSX
Previous Message Tom Lane 2002-04-24 22:08:43 Re: temp space on different location