| From: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
|---|---|
| To: | andrewbille(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17385: "RESET transaction_isolation" inside serializable transaction causes Assert at the transaction end |
| Date: | 2022-01-28 15:26:08 |
| Message-ID: | b22395d2-d432-f211-0bed-1f466df75152@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토SQL : Postg토토SQL 메일 링리스트 : 2022-01-28 이후 PGSQL-BUGS 15:26 |
Hi,
Additional information. Query
"RESET transaction_isolation;"
in previous message can be replaced to synonym
"SET transaction_isolation=DEFAULT;"
(error will be the same).
I attached file with simple fix for branch "master".
I not sure that need to use a separate block of code for the
"transaction_isolation" GUC-variable. But this is a special variable
and there are several places in the code with handling of this variable.
With best regards,
Dmitry Koval.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Fixed-reset-transaction_isolation.patch | text/plain | 1.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-28 16:15:32 | Re: BUG #17382: When vacuum full or vacuumdb - F is executed, a large number of empty files will be generated in the |
| Previous Message | Maxim Boguk | 2022-01-28 14:17:28 | Re: BUG #17386: btree index corruption after reindex concurrently on write heavy table |