Re: generating function default settings from pg_proc.dat

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: generating function default settings from pg_proc.dat
Date: 2026-03-05 23:36:54
Message-ID: 5v3ragrima26bcrrowdjuhib2ka464npeeor5fiywmhxbqi7bf@jxtyyz4ftclb
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2026-03-05 17:44:06 -0500, Tom Lane wrote:
> I wrote:
> > =?utf-8?Q?=C3=81lvaro?= Herrera <alvherre(at)kurilemu(dot)de> writes:
> >> I think this is an OK arrangement, but perhaps there should be a comment
> >> in system_views.sql about it.
>
> > Yeah, that'd be a good thing to do if we keep it like this. Perhaps
> > more or less
>
> > * Some of these views are not meant to be publicly readable. The
> > * underlying function(s) for such a view should not be publicly
> > * executable either --- but by default they will be. Don't forget to
> > * adjust function permissions (in pg_proc.dat) when adding a new view.
>
> Hearing no further comments, pushed like that.

Thanks a lot for working on this!

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-03-05 23:46:15 Re: Shutdown indefinitely stuck due to unflushed FPI_FOR_HINT record
Previous Message Robert Haas 2026-03-05 23:11:43 Re: Why clearing the VM doesn't require registering vm buffer in wal record