pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jens Lechtenboerger <lechten@wi.uni-muenster.de>
To: Greg Stark <gsstark@mit.edu>
Cc: Jan Wieck <JanWieck@Yahoo.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Lost updates vs resumable connections/transactions
Date: Thu, 16 Dec 2004 14:52:49 +0100
Message-ID: <m2y8fyl58u.fsf@pcwi4002.uni-muenster.de> (raw)
In-Reply-To: <87is73qrde.fsf@stark.xeocode.com>
References: <Pine.A41.4.58.0412091641060.68588@zivunix.uni-muenster.de>
	<41C06961.8020406@Yahoo.com>
	<87is73qrde.fsf@stark.xeocode.com>

Greg Stark <gsstark@mit.edu> writes:

> 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.

Well, I don't necessarily have to use locks.  I want any form of
concurrency control that ensures serializability.  Optimistic
approaches would be fine as well.

> 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.

But why should I have SQLRelay between me and the database?
I don't plan to use any of its "real" features.  It would just be a
proxy with a known address that maintains a database connection.
Obviously, the database server itself has a known address and
maintains database connections...

Jens




view thread (15+ messages)  latest in thread

Message-ID: <m2y8fyl58u.fsf@pcwi4002.uni-muenster.de>
Permalink:  ../m2y8fyl58u.fsf@pcwi4002.uni-muenster.de/
Also on:    postgresql.org/message-id/m2y8fyl58u.fsf@pcwi4002.uni-muenster.de

 · 

reply

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: lechten@wi.uni-muenster.de, gsstark@mit.edu, JanWieck@Yahoo.com
  Subject: Re: Lost updates vs resumable connections/transactions
  In-Reply-To: <m2y8fyl58u.fsf@pcwi4002.uni-muenster.de>

* 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