Re: [Patch] ALTER SYSTEM READ ONLY - Mailing list pgsql-hackers

From Mark Dilger
Subject Re: [Patch] ALTER SYSTEM READ ONLY
Date
Msg-id 982A276E-4A34-4693-8A0E-C9B3FBE6627D@enterprisedb.com
Whole thread Raw
In response to Re: [Patch] ALTER SYSTEM READ ONLY  (Amul Sul <sulamul@gmail.com>)
Responses Re: [Patch] ALTER SYSTEM READ ONLY  (Amul Sul <sulamul@gmail.com>)
List pgsql-hackers

> On Sep 22, 2021, at 6:39 AM, Amul Sul <sulamul@gmail.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
betweenthe session which uses cursors and the system going read-only.  Whether the session using a cursor gets a FATAL,
justan ERROR, or neither depends on where it is in the process of opening, using, closing and committing.  I think
that'sinteresting.  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






pgsql-hackers by date:

Previous
From: Amul Sul
Date:
Subject: Re: [Patch] ALTER SYSTEM READ ONLY
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: PostgreSQL 14 press release draft