pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: zuming.jiang@inf.ethz.ch
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18292: Unexpected error: "relation "hobbies_r" does not exist" caused by user-defined functions
Date: Sun, 14 Jan 2024 21:57:03 -0500
Message-ID: <1367517.1705287423@sss.pgh.pa.us> (raw)
In-Reply-To: <18292-55856fb8254c79d6@postgresql.org>
References: <18292-55856fb8254c79d6@postgresql.org>

PG Bug reporting form <noreply@postgresql.org> writes:
> My fuzzer finds a suspicious alarm in Postgres 17devel: "ERROR:  relation
> "hobbies_r" does not exist". I report it as I think it might be an
> unexpected error.

I don't see anything unexpected here: you made a transaction-local
change in search_path that renders that table invisible.  It's not
instantly obvious how the flow of control gets to a lookup of
that table after the SET LOCAL; but evidently that's happening,
and I don't feel any urge to work out the details.

(Note that if you were expecting SET LOCAL to mean "local to this
function call", you're mistaken.  You can get that effect with a SET
clause attached to the function definition; but this is not that.)

If you want people to take this sort of report seriously, you need to
analyze the behavior yourself, not expect us to look for a bug that
probably doesn't exist.

			regards, tom lane





view thread (3+ messages)  latest in thread

Message-ID: <1367517.1705287423@sss.pgh.pa.us>
Permalink:  ../1367517.1705287423@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1367517.1705287423@sss.pgh.pa.us

 · 

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: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, zuming.jiang@inf.ethz.ch, pgsql-bugs@lists.postgresql.org
  Subject: Re: BUG #18292: Unexpected error: "relation "hobbies_r" does not exist" caused by user-defined functions
  In-Reply-To: <1367517.1705287423@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