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

From Robert Haas
Subject Re: Prevent writes on large objects in read-only transactions
Date
Msg-id CA+TgmoajKyqQ6TePTgjs5hz=vr9GCs-is6MtfYcvNiRxdtfp0w@mail.gmail.com
Whole thread Raw
In response to Re: Prevent writes on large objects in read-only transactions  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Prevent writes on large objects in read-only transactions  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, May 28, 2022 at 5:01 AM Michael Paquier <michael@paquier.xyz> wrote:
> Well, there is an actual risk to break applications that have worked
> until now for a behavior that has existed for years with zero
> complaints on the matter, so I would leave that alone.  Saying that, I
> don't really disagree with improving the error messages a bit if we
> are in recovery.

On the other hand, there's a good argument that the existing behavior
is simply incorrect.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ParseTzFile doesn't FreeFile on error
Next
From: Tomas Vondra
Date:
Subject: Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)