Horton

Re: Prevent writes on large objects in read-only transactions

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Yugo NAGATA <nagata@sraoss.co.jp>, pgsql-hackers@postgresql.org
Date: 2022-05-31T01:46:27Z
Lists: 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

Commits

  1. Prevent write operations on large objects in read-only transactions

  2. Fix comment in regression tests for large objects