| From: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Documenting when to retry on serialization failure |
| Date: | 2022-01-04 11:49:28 |
| Message-ID: | CANbhV-FwS+MMyYEONPw_EQ-NSd41bBhdxAZMWDDONaqxfbEivA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 16 Dec 2021 at 06:05, Greg Stark <stark(at)mit(dot)edu> wrote:
> So a lot of users are probably looking at something like "BEGIN;
> SELECT create_customer_order(....); COMMIT" and wondering why the
> server can't handle automatically retrying the query if they get an
> isolation failure.
I agree with you that it would be desirable to retry for the simple
case of an autocommit/single statement transaction run with
default_transaction_isolation = 'serializability'.
The most important question before we take further action is whether
this would be correct to do so, in all cases.
Some problem cases would help us decide either way.
--
Simon Riggs http://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | osumi.takamichi@fujitsu.com | 2022-01-04 11:52:21 | RE: Failed transaction statistics to measure the logical replication progress |
| Previous Message | osumi.takamichi@fujitsu.com | 2022-01-04 11:47:26 | RE: Failed transaction statistics to measure the logical replication progress |