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(dot)albe(at)cybertec(dot)at>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Yushu Chen <gentcys(at)gmail(dot)com>, katja(dot)henke(at)foo(dot)ag, PostgreSQL Bug List <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
Date: 2025-09-08 08:31:11
Message-ID: 1a10058e3803eb733a98323e501d33e6da5d5db2.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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 simple
> alternatives to use when this functionality is required it's got to be easier
> 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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2025-09-08 15:10:11 Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
Previous Message Kristo Marijo 2025-09-08 06:39:47 AW: BUG #19043: jdbc connection url is not case insensitive