On Thu, Jul 28, 2022 at 9:19 AM Jacob Champion <jchamp...@timescale.com> wrote:
> On Thu, Jul 21, 2022 at 4:29 PM Jacob Champion <jchamp...@timescale.com> 
> wrote:
> > v4 attempts to fix this by letting the check hooks pass
> > MCXT_ALLOC_NO_OOM to pg_clean_ascii(). (It's ignored in the frontend,
> > which just mallocs.)
>
> Ping -- should I add an open item somewhere so this isn't lost?

Trying again. Peter, is this approach acceptable? Should I try something else?

Thanks,
--Jacob


Reply via email to