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

On Sat, Sep 26, 2026 at 6:34 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> On Tue, Sep 22, 2026 at 10:56 PM Nisha Moond <nisha.moond412@gmail.com> wrote:
> >
>
> > What remains:
> > Together these cover every built-in type, scalar and container alike.
> > The one case neither handles is a user-defined type whose own output
> > function renders far more than its input; no cap on the input can
> > detect that. Such a function has to be written in C, since a SQL
> > function cannot return cstring, so it sits at the same level as
> > replacing a built-in output function. IMO, that seems acceptable to
> > leave for now.
> >
>
> I have tried to verify this with the attached extension (written with
> the help of AI).
>

Forgot to attach the extension in the previous email, doing now.

--
With Regards,
Amit Kapila.