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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yushu Chen <gentcys(at)gmail(dot)com>
Cc: katja(dot)henke(at)foo(dot)ag, 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-05 12:17:33
Message-ID: 8dec121e2d3bfc1149d36359345fbce1faa087aa.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 2025-09-04 at 11:24 -0400, Tom Lane wrote:
> Given that recursive SQL functions are a tiny-minority use case
> and there's already a perfectly serviceable way to make them
> (ie use an old-style body), I seriously doubt that we'll do
> anything about this request.

Sure, but creating a dump that will fail to load is not good.
I don't have a smarter idea that dumping standard SQL functions
in two statements like you suggested...

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2025-09-05 12:55:53 Re: BUG #19034: Recursive function with sql_body can replace an existing function but can not be created on it's own
Previous Message PG Bug reporting form 2025-09-05 06:28:15 BUG #19043: jdbc connection url is not case insensitive