| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Joe Wildish <joe-postgresql(dot)org(at)elusive(dot)cx>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Implementing SQL ASSERTION |
| Date: | 2018-03-09 17:37:23 |
| Message-ID: | CA+TgmoZNCL9oB+mnYhZr_U7DEcQSsas-tWiZu6ocn=1=PLjdPA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 15, 2018 at 11:35 AM, David Fetter <david(at)fetter(dot)org> wrote:
> - We follow the SQL standard and make SERIALIZABLE the default
> transaction isolation level, and
The consequences of such a decision would include:
- pgbench -S would run up to 10x slower, at least if these old
benchmark results are still valid:
- pgbench without -S would fail outright, because it doesn't have
provision to retry failed transactions.
https://commitfest.postgresql.org/16/1419/
- Many user applications would probably also experience similar difficulties.
- Parallel query would no longer work by default, unless this patch
gets committed:
https://commitfest.postgresql.org/17/1004/
I think a good deal of work to improve the performance of serializable
would need to be done before we could even think about making it the
default -- and even then, the fact that it really requires the
application to be retry-capable seems like a pretty major obstacle.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2018-03-09 17:54:46 | Re: Faster inserts with mostly-monotonically increasing values |
| Previous Message | Emre Hasegeli | 2018-03-09 17:05:32 | Re: Precision loss casting float to numeric |