Message-ID: <1a10058e3803eb733a98323e501d33e6da5d5db2.camel@cybertec.at>
Subject: Re: BUG #19034: Recursive function with sql_body can replace an
 existing function but can not be created on it's own
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: "David G. Johnston" <david.g.johnston@gmail.com>, Tom Lane
	 <tgl@sss.pgh.pa.us>
Cc: Yushu Chen <gentcys@gmail.com>, katja.henke@foo.ag, PostgreSQL Bug List
	 <pgsql-bugs@lists.postgresql.org>
Date: Mon, 08 Sep 2025 10:31:11 +0200
In-Reply-To: 
 <CAKFQuwaFZzT3XCQiyX47Q6sP735CHBxONF6NWzB=0ikssf=3pQ@mail.gmail.com>
References: <19034-de0857b4f94ec10c@postgresql.org>
	 <CAP5x3pZvk6D9b9mmKBEYKqZvJcDpH5OfZ419aVgzr+xXpo4O=w@mail.gmail.com>
	 <1030106.1756999498@sss.pgh.pa.us>
	 <8dec121e2d3bfc1149d36359345fbce1faa087aa.camel@cybertec.at>
	 <CAKFQuwYfD-JE8svtfJcgCHce=8ag5000Gms4hr=JXH+L8CWhPQ@mail.gmail.com>
	 <c48613a5ef709ae349e7f9509fa52b578b0eaecb.camel@cybertec.at>
	 <CAKFQuwb7Kk-JKY3nVX+RMTM1jnBxLK-z0erGW4bMozHf1u=2zQ@mail.gmail.com>
	 <341490.1757284616@sss.pgh.pa.us>
	 <CAKFQuwaFZzT3XCQiyX47Q6sP735CHBxONF6NWzB=0ikssf=3pQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-2.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/1a10058e3803eb733a98323e501d33e6da5d5db2.camel%40cybertec.at>
Precedence: bulk

On Sun, 2025-09-07 at 15:50 -0700, David G. Johnston wrote:
> While I agree making it must work would be nice given the presence of sim=
ple
> alternatives to use when this functionality is required it's got to be ea=
sier
> to detect and prohibit creation.

Perhaps that is the way to go, although it would not make me happy.
But that still leaves the problem of what to do with a database that
already contains recursive SQL functions during pg_dump/pg_restore.

Yours,
Laurenz Albe