Horton

Re: BUG #17646: create rule named "_RETURN" will cause pg core

Ilya Anfimov <ilan@tzirechnoy.com>

View thread View on postgr.es
From: Ilya Anfimov <ilan@tzirechnoy.com>
To: pgsql-bugs@lists.postgresql.org
Date: 2022-10-17T14:38:38Z
Lists: pgsql-bugs 
On Mon, Oct 17, 2022 at 12:03:15PM +0000, PG Bug reporting form wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      17646
> Logged by:          kui liu
> Email address:      liukui@kingbase.com.cn
> PostgreSQL version: 15.0
> Operating system:   linux
> Description:        
> 
> Hi, I encounter an error, it may be a bug,  thx.
> 
> 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;
> select * from v1;
> 
> execute up sql, will get this error
> 
> server closed the connection unexpectedly
>         This probably means the server terminated abnormally
>         before or while processing the request.
> The connection to the server was lost. Attempting reset: Failed.
> The connection to the server was lost. Attempting reset: Failed.
> !?>

btw, I'm confirming the bug for postgres from at least 8.4 to 14.

Version 11 and less instead of segfault prints someting like:

ilan=*# select * from v1;
ERROR:  could not open file "base/24576/57373": No such file or directory

>

Commits

  1. Reject non-ON-SELECT rules that are named "_RETURN".

  2. Guard against table-AM-less relations in planner.