| From: | Mark Dilger <mark(dot)dilger(at)enterprisedb(dot)com> |
|---|---|
| To: | Amul Sul <sulamul(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [Patch] ALTER SYSTEM READ ONLY |
| Date: | 2021-09-22 14:03:15 |
| Message-ID: | 982A276E-4A34-4693-8A0E-C9B3FBE6627D@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On Sep 22, 2021, at 6:39 AM, Amul Sul <sulamul(at)gmail(dot)com> wrote:
>
> Yes, that is a bit longer, here is the snip from v35-0010 patch
Right, that's longer, and only tests one interaction. The isolation spec I posted upthread tests multiple interactions between the session which uses cursors and the system going read-only. Whether the session using a cursor gets a FATAL, just an ERROR, or neither depends on where it is in the process of opening, using, closing and committing. I think that's interesting. If the implementation of the ALTER SESSION READ ONLY feature were to change in such a way as, for example, to make the attempt to open the cursor be a FATAL error, you'd see a change in the test output.
—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2021-09-22 14:17:07 | Re: PostgreSQL 14 press release draft |
| Previous Message | Amul Sul | 2021-09-22 13:39:04 | Re: [Patch] ALTER SYSTEM READ ONLY |