From: Greg Stark <gsstark@mit.edu>
To: Jan Wieck <JanWieck@Yahoo.com>
Cc: Jens Lechtenbörger <lechtej@uni-muenster.de>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Lost updates vs resumable connections/transactions
Date: 15 Dec 2004 14:43:41 -0500
Message-ID: <87is73qrde.fsf@stark.xeocode.com> (raw)
In-Reply-To: <41C06961.8020406@Yahoo.com>
References: <Pine.A41.4.58.0412091641060.68588@zivunix.uni-muenster.de>
<41C06961.8020406@Yahoo.com>
Jan Wieck <JanWieck@Yahoo.com> writes:
> Even applications that have statefull enduser terminals (like SAP R/3 for
> example) never allow an open transaction over user interaction.
I'm not sure using SAP as your paragon of design excellence is a wise choice
here. From what I understand SAP implemented its own locking system because
the database it was based on didn't offer any locking at all.
But your basic point is sound. For a web site I would definitely avoid using
anything like database locks and even avoid doing anything with application
locks if possible.
If you really really want to expose the database session state I think he's on
the right track using SQLRelay. This would let him handle reconnecting a user
with her session even if she's connecting to a different Apache process.
I suspect the database wouldn't really be able to suspend a database
connection using any less memory than just keeping the entire backend process
with its session around anyways.
--
greg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: gsstark@mit.edu, JanWieck@Yahoo.com, lechtej@uni-muenster.de
Subject: Re: Lost updates vs resumable connections/transactions
In-Reply-To: <87is73qrde.fsf@stark.xeocode.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox