| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Lincoln Yeoh <lyeoh(at)pop(dot)jaring(dot)my>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, pgsql-general(at)postgresql(dot)org, Greg Stark <gsstark(at)mit(dot)edu> |
| Subject: | Re: PREPARE TRANSACTION and webapps |
| Date: | 2005-11-16 17:05:11 |
| Message-ID: | 87veysttfc.fsf@stark.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> > This could be useful if you want to have X pending database transactions
> > and Y max concurrent database connections, where X is significantly greater
> > than Y (magnitudes higher?).
>
> I don't think the prepared-xacts facility has the performance that would
> be needed to sustain that kind of usage. Suspend/resume would not be
> all that cheap, and a suspended transaction would still hold a lot of
> resources (locks mostly).
Well it'll be better than having to maintain a connection for each
transaction.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-11-16 17:05:36 | Re: Rebranding PostgreSQL |
| Previous Message | Martijn van Oosterhout | 2005-11-16 17:04:56 | Re: PREPARE TRANSACTION and webapps |