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

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Prevent writes on large objects in read-only transactions
Date: 2022-05-27 12:02:24
Message-ID: fa456f80854a60819111518f187c5c446bf3e31e.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2022-05-27 12:03:21 Re: allow building trusted languages without the untrusted versions
Previous Message Thomas Munro 2022-05-27 11:54:24 Re: "ERROR: latch already owned" on gharial