Re: Statement-level rollback
| От | Tom Lane |
|---|---|
| Тема | Re: Statement-level rollback |
| Дата | |
| Msg-id | 22540.1544216573@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Statement-level rollback (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: Statement-level rollback
|
| Список | pgsql-hackers |
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Well, look at this from this point of view: EnterpriseDB implemented
> this because of customer demand (presumably). Fujitsu also implemented
> this for customers. The pgjdbc driver implemented this for its users.
> Now 2ndQuadrant also implemented this, and not out of the goodness of
> our hearts. Is there any room to say that there is no customer demand
> for this feature?
Yeah, but there is also lots of demand for stability in basic
transactional semantics. I refer you again to the AUTOCOMMIT business;
there were a lot of claims that that wouldn't break too much, and they
were all wrong.
regards, tom lane
В списке pgsql-hackers по дате отправления: