Re: Prevent writes on large objects in read-only transactions - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Prevent writes on large objects in read-only transactions
Date
Msg-id YpVzcxR6yYjmEPN6@paquier.xyz
Whole thread Raw
In response to Re: Prevent writes on large objects in read-only transactions  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
On Fri, May 27, 2022 at 02:02:24PM +0200, Laurenz Albe wrote:
> On Fri, 2022-05-27 at 15:30 +0900, Yugo NAGATA wrote:
>> Currently, lo_creat(e), lo_import, lo_unlink, lowrite, lo_put,
>> and lo_from_bytea are allowed even in read-only transactions.
>> By using them, pg_largeobject and pg_largeobject_metatable can
>> be modified in read-only transactions and the effect remains
>> after the transaction finished. Is it unacceptable behaviours,
>> isn't it?
>
> +1

And I have forgotten to add your name as a reviewer.  Sorry about
that!
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Prevent writes on large objects in read-only transactions
Next
From: Thomas Munro
Date:
Subject: Failures in sto_using_cursor test