Re: Proposal: Conflict log history table for Logical Replication - Mailing list pgsql-hackers

On Tue, Jun 16, 2026 at 9:56 AM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Tue, Jun 16, 2026 at 9:27 AM vignesh C <vignesh21@gmail.com> wrote:
> >
> > Shouldn’t creating a view also be allowed for the same reason?
> >
> > The function is permitted because it only performs a SELECT on the
> > conflict log table, and such read operations are allowed. A view
> > likewise represents a stored query definition and does not modify the
> > conflict schema or its underlying tables. Given that direct queries on
> > the conflict log tables are already permitted, allowing users to
> > define views over them is consistent with the same rationale applied
> > to functions.
>
> Whats is the behavior of toast table w.r.t the function vs view?
>

I think sticking to the minimum set of commands that are required for
the user to monitor/maintain CLT should be a good goal for the first
version. We can evaluate to allow other commands based on real user
need and its impact on the functionality. So, it is okay to block even
the view on CLT for now.

--
With Regards,
Amit Kapila.