From: Tom Lane <tgl@sss.pgh.pa.us>
To: liukui@kingbase.com.cn
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17646: create rule named "_RETURN" will cause pg core
In-reply-to: <17646-70c93cfa40365776@postgresql.org>
References: <17646-70c93cfa40365776@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 17 Oct 2022 12:03:15 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2164335.1666016275.1@sss.pgh.pa.us>
Date: Mon, 17 Oct 2022 10:17:55 -0400
Message-ID: <2164336.1666016275@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2164336.1666016275%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> here is a test case

> create table t (id integer);
> create view v1 as select * from t;
> create or replace rule "_RETURN" as on UPDATE to v1 do instead select * from
> t;

Meh.  We should be preventing you from doing that.

(Although the core dump is also not great --- something should've noticed
the bogosity of the plan earlier than this.)

			regards, tom lane