From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: d.koval@postgrespro.ru
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
Date: Tue, 05 Jul 2022 23:56:18 -0400
Message-ID: <2074692.1657079778@sss.pgh.pa.us> (raw)
In-Reply-To: <YsUEU/NFv1YDo12l@paquier.xyz>
References: <17539-37e89c604ebc0e02@postgresql.org>
<2029909.1657060342@sss.pgh.pa.us>
<YsUEU/NFv1YDo12l@paquier.xyz>
Michael Paquier <michael@paquier.xyz> writes:
> Agreed. But isn't the proposal of Dmitry to switch the assertion to
> an error a good thing though?
If you're excited enough about it to commit it, I won't stand in
the way. But I know that there's plenty of other stuff you can
break with a crafted opclass definition.
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, michael@paquier.xyz, d.koval@postgrespro.ru, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17539: Assert after CREATE OPERATOR CLASS command
In-Reply-To: <2074692.1657079778@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox