| From: | Andrew Rawnsley <ronz(at)ravensfield(dot)com> |
|---|---|
| To: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: postgresql idle |
| Date: | 2004-04-29 19:57:59 |
| Message-ID: | 83B09A16-9A17-11D8-BDB5-000393A47FCC@ravensfield.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
I find that some clients (DBVisualizer for one) do exactly that -
execute the COMMIT;BEGIN sequence, and leaves idle
transactions on a consistent basis.
On Apr 29, 2004, at 3:19 PM, Andrew Sullivan wrote:
> On Thu, Apr 29, 2004 at 02:04:47PM -0400, Jon Pastore wrote:
>> pgsql thought there was a transaction in progress and was waiting
>> for it to complete when in fact the commit had already taken place.
>
> Come again? That doesn't sound possible. What ismore likely is that
> somebody issues COMMIT;BEGIN; all at once. You get one transaction
> through, but you still end up idle in transaciton.
>
> A
>
> --
> Andrew Sullivan | ajs(at)crankycanuck(dot)ca
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
> majordomo(at)postgresql(dot)org)
>
--------------------
Andrew Rawnsley
President
The Ravensfield Digital Resource Group, Ltd.
(740) 587-0114
www.ravensfield.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-04-29 20:23:43 | Re: Syntax error at or near "$1" |
| Previous Message | Gregory S. Williamson | 2004-04-29 19:53:40 | "Idle in Transaction" and hung connections |