Re: Potential security risk associated with function call - Mailing list pgsql-hackers

From Jet
Subject Re: Potential security risk associated with function call
Date
Msg-id tencent_6AE511D377F044C8157B6FF9@qq.com
Whole thread Raw
In response to Re: Potential security risk associated with function call  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Potential security risk associated with function call
List pgsql-hackers
> but the 2026 reality is that someone would
> just say "deploy an AI agent to check whether the code is safe for the
> definition," and that might actually work in practical cases, but
> we're not going to add a call-out to Claude as part of the CREATE
> FUNCTION statement.
I notice the potential problem just because using Claude to write a simple
extension. And it works well on testing enviroment. But when take over the
Claude generated extenion to dev enviroment, the server crashed. 
More and more people will use AI to generate codes, that's the trend, but AI 
will make mistakes, and may leave many potention risks. So I suppose as the
base platform, we should try our best efforts to make it more robust.

Regards,
Jet
Halo Tech

pgsql-hackers by date:

Previous
From: Tender Wang
Date:
Subject: [PATCH] Simplify trivial shmem size calculations
Next
From: Daniel Gustafsson
Date:
Subject: Re: Serverside SNI support in libpq