Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: why postgresql over other RDBMS
- From: PFC <lists(at)peufeu(dot)com>
- To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "A.M." <agentm(at)themactionfaction(dot)com>
- Cc: "pgsql-general general" <pgsql-general(at)postgresql(dot)org>
- Subject: Re: why postgresql over other RDBMS
- Date: Fri, 25 May 2007 00:12:34 +0200
- Message-id: <op(dot)tsuqm8nzcigqcu(at)apollo13>
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".
- Follow-Ups:
- Re: why postgresql over other RDBMS
- From: A.M.
- Re: why postgresql over other RDBMS
- References:
- why postgresql over other RDBMS
- From: Jasbinder Singh Bali
- Re: why postgresql over other RDBMS
- From: Tom Allison
- Re: why postgresql over other RDBMS
- From: Richard Huxton
- Re: why postgresql over other RDBMS
- From: Alexander Staubo
- Re: why postgresql over other RDBMS
- From: Wiebe Cazemier
- Re: why postgresql over other RDBMS
- From: A.M.
- Re: why postgresql over other RDBMS
- From: Alvaro Herrera
- why postgresql over other RDBMS
- Prev by Date: [no subject]
- Next by Date: Re: why postgresql over other RDBMS
- Previous by thread: Re: why postgresql over other RDBMS
- Next by thread: Re: why postgresql over other RDBMS
- Indexes: