Re: generating function default settings from pg_proc.dat

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generating function default settings from pg_proc.dat
Date: 2026-02-17 21:59:46
Message-ID: 1905096.1771365586@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> That makes sense. I haven't tested it, but the code looks pretty sane.
> Nice job. I guess if we ever want to specify a default that's not a
> Const for some reason we'd have to fall back on the system_views
> mechanism. But that's not very likely.

Right, the idea of this patch is to make the common cases easy
without making uncommon cases any worse than they were. We have
enough experience now with default arguments to be pretty sure
that this will cover 90%-plus of the need.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-02-17 22:24:58 add assertion for palloc in signal handlers
Previous Message Andres Freund 2026-02-17 21:56:11 Re: BackgroundPsql swallowing errors on windows