From: | David Helgason <david(at)uti(dot)is> |
---|---|
To: | A(dot)Mous <a(dot)mous(at)shaw(dot)ca> |
Cc: | Doug McNaught <doug(at)mcnaught(dot)org>, postgres list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Transaction rollback - newbie |
Date: | 2004-11-10 03:15:22 |
Message-ID: | C1CB03F2-32C6-11D9-9F90-000A9566DA8A@uti.is |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Anytime data changes in Postgres, the old rows are still on the disk.
This is true regardless if the transaction rolls back.
Read in the docs about vacuuming, which is a process that cleans this
up.
Regards,
d.
--
David Helgason,
Business Development et al.,
Over the Edge I/S (http://otee.dk)
Direct line +45 2620 0663
Main line +45 3264 5049
On 10. nov 2004, at 03:38, Doug McNaught wrote:
> "A. Mous" <a(dot)mous(at)shaw(dot)ca> writes:
>
>> Hi,
>>
>> I've got clients connected to pgsql via ODBC. If they lose their
>> connection
>> abruptly, all un-committed transactions are automatically rolled-back
>> (I'm
>> assuming) but is there anything left behind that needs to be cleaned
>> up on
>> the server side with regards to the uncommitted transaction(s)?
>
> No. When the connection goes away, the backend will log an error,
> roll back the transaction and exit cleanly.
>
> -Doug
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to
> majordomo(at)postgresql(dot)org
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gary L. Burnore | 2004-11-10 03:31:08 | Re: Important Info on comp.databases.postgresql.general |
Previous Message | Doug McNaught | 2004-11-10 02:38:28 | Re: Transaction rollback - newbie |