From: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Transactions and web applications |
Date: | 2000-06-23 06:46:38 |
Message-ID: | 3.0.5.32.20000623144638.0090f340@pop.mecomb.po.my |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi people,
What are the recommended ways to do transactions in web applications?
Right now I have persistent database connections, but currently they are
shared by multiple sessions. So I make sure that database level
transactions are closed after each page/http request.
In theory I could tie database connections to sessions, but then if I have
1000 outstanding (not necessarily active) sessions that would mean 1000
database connections, and 1000 postgres backend processes right? Ouch!
Because of this it looks like I may actually have to do application level
transactions instead of being able to rely solely on database level
transactions.
Am I missing something? Are there better/good alternatives?
Would it be possible to "name" transactions and continue them from other
database connections? Sounds impractical tho- what happens if two
connections try to continue a transaction at overlapping times :) (user
opens up multiple browsers from one page).
Cheerio,
Link.
From | Date | Subject | |
---|---|---|---|
Next Message | Dustin Sallings | 2000-06-23 07:31:25 | Re: How to select a row and an adjacent row? |
Previous Message | Lincoln Yeoh | 2000-06-23 06:21:17 | Re: How to select a row and an adjacent row? |