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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Prevent writes on large objects in read-only transactions
Date: 2022-05-31 18:40:43
Message-ID: CA+TgmoajKyqQ6TePTgjs5hz=vr9GCs-is6MtfYcvNiRxdtfp0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 28, 2022 at 5:01 AM Michael Paquier <michael(at)paquier(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2022-05-31 18:44:26 Re: Improving connection scalability (src/backend/storage/ipc/procarray.c)
Previous Message Tom Lane 2022-05-31 18:21:28 Re: ParseTzFile doesn't FreeFile on error