Re: why postgresql over other RDBMS

From: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
To: pgsql-general general <pgsql-general(at)postgresql(dot)org>
Subject: Re: why postgresql over other RDBMS
Date: 2007-05-24 22:14:58
Message-ID: F89FBDDA-8F33-4517-AA88-118A97EB07D0@themactionfaction.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On May 24, 2007, at 18:12 , PFC wrote:

>
>>> Indeed. Wouldn't it be a cool feature to persists transaction states
>>> across connections so that a new connection could get access to a
>>> sub-
>>> transaction state? That way, you could make your schema changes and
>>> test them with any number of test clients (which designate the state
>>> to connect with) and then you would commit when everything works.
>
> Actually you can hack this by starting your webserver with only 1
> thread, use persistent connections, and disable all commits in the
> application.
> But I'd call that "a very hackish hack".

Not really- then I can't use any transactions, in which case, I might
as well use MySQL. I would like to be able to pass transaction state
between connections.

-M

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Chris Browne 2007-05-24 22:21:24 Re: why postgresql over other RDBMS
Previous Message PFC 2007-05-24 22:12:34 Re: why postgresql over other RDBMS