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

From Amul Sul
Subject Re: [Patch] ALTER SYSTEM READ ONLY
Date
Msg-id CAAJ_b94r=qBUPwPBe3FTttK5Lwh=td9ZhD5pMoXt4EQv8JtgAw@mail.gmail.com
Whole thread Raw
In response to Re: [Patch] ALTER SYSTEM READ ONLY  (Mark Dilger <mark.dilger@enterprisedb.com>)
List pgsql-hackers
On Wed, Sep 22, 2021 at 7:33 PM Mark Dilger
<mark.dilger@enterprisedb.com> wrote:
>
>
>
> > 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
interactionsbetween the session which uses cursors and the system going read-only.  Whether the session using a cursor
getsa 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. 
>

Agreed.

Regards,
Amul



pgsql-hackers by date:

Previous
From: wenjing
Date:
Subject: Re: [Proposal] Global temporary tables
Next
From: wenjing
Date:
Subject: Re: [Proposal] Global temporary tables