From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Subject: | Re: Regression tests vs SERIALIZABLE |
Date: | 2021-03-15 10:51:13 |
Message-ID: | CA+hUKG+G_MR6f6T+Ncd_jfei0M4za1usr7iDM50D0OYDTuH+1g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 15, 2021 at 5:24 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> However, since commit 862ef372d6b, there *is* one test that fails if
> you run make installcheck against a cluster running with -c
> default_transaction_isolation=serializable: transaction.sql. Is that
> a mistake? Is it a goal to be able to run this test suite against all
> 3 isolation levels?
Here's a fix.
Attachment | Content-Type | Size |
---|---|---|
0001-Fix-transaction.sql-tests-in-higher-isolation-levels.patch | text/x-patch | 2.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2021-03-15 10:57:45 | Re: Hybrid Hash/Nested Loop joins and caching results from subplans |
Previous Message | Guillaume Lelarge | 2021-03-15 10:37:02 | Re: Extensions not dumped when --schema is used |