public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: [email protected]
Cc: [email protected]
Subject: Re: BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.
Date: Wed, 10 Jun 2026 10:38:56 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

PG Bug reporting form <[email protected]> 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

view thread (2+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: BUG #19515: Creating a faulty BRIN operator class can cause the server to crash when used.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox