Re: BUG #16190: The usage of NULL pointer in refint.c

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, starbugs(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16190: The usage of NULL pointer in refint.c
Date: 2020-01-06 17:44:43
Message-ID: 20200106174443.3pwnmshbxrbwggrm@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On 2020-01-06 01:21:35 -0500, Tom Lane wrote:
> Michael Paquier <michael(at)paquier(dot)xyz> writes:
> > ... There could be also an argument to just
> > remove the module per the lack of attention it is getting, though it
> > is still useful as an example of use for SPI, and the docs mention
> > it for that.
>
> The regression tests use refint too. Still, it's not production-grade
> code by any means, and I'm not sure if there's much point in making
> it so. I won't stand in the way if somebody else wants to ;-)

I think we should consider either moving this out of contrib, or fixing
it up. test/example code is fine, but contrib gets installed by default
for a lot of people... And yea, this isn't just about contrib/spi.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff Janes 2020-01-06 17:50:48 Re: BUG #16183: PREPARED STATEMENT slowed down by jit
Previous Message Tom Lane 2020-01-06 17:33:47 Re: Assert failure due to "drop schema pg_temp_3 cascade" for temporary tables and \d+ is not showing any info after drooping temp table schema