Postgres Pro
Downloads
Home   >   mailing lists

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

From Laurenz Albe
Subject Re: Prevent writes on large objects in read-only transactions
Date
Msg-id fa456f80854a60819111518f187c5c446bf3e31e.camel@cybertec.at
Whole thread Raw
In response to Prevent writes on large objects in read-only transactions  (Yugo NAGATA <nagata@sraoss.co.jp>)
Responses Re: Prevent writes on large objects in read-only transactions
List pgsql-hackers
Tree view 
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

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: "ERROR: latch already owned" on gharial
Next
From: Peter Eisentraut
Date:
Subject: Re: allow building trusted languages without the untrusted versions