Re: BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used. - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.
Date
Msg-id 1286399.1781102336@sss.pgh.pa.us
Whole thread
In response to BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> Creating a BRIN operator class with a support function that has a wrong
>   signature (e.g. accepting text instead of internal) succeeds at DDL time,
>   but crashes the server when a BRIN index using that opclass is created.

This is not a Postgres bug.  The reason that opclass creation is
restricted to superusers is that the system trusts opclasses to
behave according to spec.  We'd check that rather than just assume it
if it were practical to do so, but it's not really (see the halting
problem for starters).

We could close a small fraction of the possible crash causes by
improving assignProcTypes, but that would be a feature improvement
not a bug fix.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: BUG #19484: Segmentation fault triggered by FDW
Next
From: Tender Wang
Date:
Subject: Re: BUG #19517: Eager Aggregation produces wrong count(*) when pushed into RHS of Hash Semi Join