agora inbox for pgsql-hackers@postgresql.org  
help / color / mirror / Atom feed
From: Nathan Bossart <nathandbossart@gmail.com>
To: solai v <solai.cdac@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: pgsql-hackers@postgresql.org
Subject: Re: problems with toast.* reloptions
Date: Tue, 26 May 2026 09:23:11 -0500
Message-ID: <ahWsz2D9quWBgZ7s@nathan> (raw)
In-Reply-To: <CAF0whuenaSkNNVXhk9207Q_fR57SLYbi_dV-p9Mer8=FjM7iwg@mail.gmail.com>
References: <aFRxC1W_kZU9OjJ9@nathan>
	<aFTB8bs_u5WyBReK@paquier.xyz>
	<aFnATDLLdP0m-fGb@nathan>
	<aFozXwRQu3LaDELy@paquier.xyz>
	<aFrUkYVyATVk2nsD@nathan>
	<afUd-A4CvaGc9se7@nathan>
	<afi-G3xIntN-pUjR@nathan>
	<afuzQuX17qpVugnY@nathan>
	<CAF0whuenaSkNNVXhk9207Q_fR57SLYbi_dV-p9Mer8=FjM7iwg@mail.gmail.com>

On Tue, May 26, 2026 at 11:25:39AM +0530, solai v wrote:
> I tested the TOAST reloptions behavior locally on current HEAD and was
> able to reproduce the inheritance and RESET scenarios discussed in the
> thread.
> From my testing, explicit toast.reloptions behave independently from
> parent reloptions. After setting both parent and TOAST vacuum_truncate
> values, RESET(vacuum_truncate) on the parent table cleared only the
> parent reloption while the explicit TOAST reloption remained intact.
> I also tried applying the v1-0004 patch in a clean worktree, but most
> hunks in vacuum.c and autovacuum.c no longer apply cleanly against
> current HEAD due to code drift. From inspecting the rejected hunks, it
> looks like the patch approach was to dynamically combine parent and
> TOAST reloptions during VACUUM/autovacuum execution instead of copying
> inherited reloptions directly into the TOAST relation.

I humbly encourage you to read the rest of the thread.  In particular, I'm
curious whether anyone would object to removing the TOAST reloptions.

-- 
nathan





view thread (44+ messages)  latest in thread

Message-ID: <ahWsz2D9quWBgZ7s@nathan>
Permalink:  ../ahWsz2D9quWBgZ7s@nathan/
Also on:    postgresql.org/message-id/ahWsz2D9quWBgZ7s@nathan

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, solai.cdac@gmail.com, michael@paquier.xyz
  Subject: Re: problems with toast.* reloptions
  In-Reply-To: <ahWsz2D9quWBgZ7s@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox