Re: Potential security risk associated with function call

From: Jet <zhangchenxi(at)halodbtech(dot)com>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Potential security risk associated with function call
Date: 2026-03-10 12:44:46
Message-ID: tencent_62EB6CDE73ED1FFC4CAD7A3B@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > > It is the explicit responsibility of
> > > the superuser to make sure the functions they create using untrusted
> > > languages are correct and execute safely when called by PostgreSQL.
> > But the question is how can a superuser know the "internal" and "c" functions
> > implementation details? He will not know whether the code has !PG_ARGISNULL(...),
> > and create a harmful function accidentally...

> I think our global assumption is that superuser is super-wise and
> knows everything

Totally agreed ...

Jet
Halo Tech

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message vignesh C 2026-03-10 12:49:34 Re: Skipping schema changes in publication
Previous Message Kirill Reshke 2026-03-10 12:39:28 Re: Potential security risk associated with function call