| From: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
|---|---|
| To: | "Jan(dot)Lindgren" <jan(dot)lindgren(at)stabilizer(dot)se> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Session disconnected |
| Date: | 2003-03-18 17:25:45 |
| Message-ID: | 1048008345.23066.1453.camel@camel |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2003-03-13 at 05:28, Jan.Lindgren wrote:
> Hi,
> I got a question on how postgres handle an interrupted transaction,
> regarding rollback, commit.
>
> We do have a rather unstable connection to our db and sometime a
> transaction/session will be disconnected but the process is still
> visible on the server.
>
> How will postgres handle an update transaction from a client to the
> server that is disconnected?
> - will the query be rollbacked automatically ??
> - is it safe to just kill the hanging process on the server?
>
More or less yes. Without getting too far into the pg internals,
understand that any information written in the database is not marked as
valid until it is given a commit. Eventually vacuum will notice that the
transaction tied to the entry is no longer valid, and will remove the
dead weight.
Robert Treat
| From | Date | Subject | |
|---|---|---|---|
| Next Message | lists | 2003-03-18 18:05:38 | Problem restoring a database |
| Previous Message | Robert Treat | 2003-03-18 17:21:14 | Re: Problem accessing database using DB Visualizer |