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

From: Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "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-07-04 07:34:07
Message-ID: 20220704163407.c2815bb7878f21a509f59f7a@sraoss.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 4 Jul 2022 15:51:32 +0900
Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> On Wed, Jun 29, 2022 at 05:29:50PM +0900, Yugo NAGATA wrote:
> > Thank you for reviewing the patch. I attached the updated patch.
>
> Thanks for the new version. I have looked at that again, and the set
> of changes seem fine (including the change for the alternate output).
> So, applied.

Thanks!

--
Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2022-07-04 07:37:09 Re-order "disable_on_error" in tab-complete COMPLETE_WITH
Previous Message Michael Paquier 2022-07-04 06:59:55 Re: Allowing REINDEX to have an optional name