Re: Potential security risk associated with function call
| От | Jet |
|---|---|
| Тема | Re: Potential security risk associated with function call |
| Дата | |
| Msg-id | tencent_6AE511D377F044C8157B6FF9@qq.com обсуждение исходный текст |
| Ответ на | Re: Potential security risk associated with function call (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Potential security risk associated with function call
|
| Список | 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 по дате отправления: