Recommend to always label the functions with the strictest volatility #255

steve-chavez · 2019-09-18T15:50:45Z

Having VOLATILE functions can have performance impacts. See PostgREST/postgrest#1378 (comment).

Not sure for now where would this go, perhaps a best practices explanation.

(Recommend to use STABLE/IMMUTABLE where possible)

steve-chavez mentioned this issue Feb 13, 2020

Change to api.rst to resolve issue #297 #303

Merged

steve-chavez added the rpc function call label Dec 30, 2021

steve-chavez mentioned this issue Dec 30, 2021

SQL function can get called twice per RPC call, depending on Prefer: count parameter PostgREST/postgrest#2108

Closed

wolfgangwalther mentioned this issue Feb 20, 2024

Document performance considerations PostgREST/postgrest#3246

Open

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Recommend to always label the functions with the strictest volatility #255

Recommend to always label the functions with the strictest volatility #255

steve-chavez commented Sep 18, 2019 •

edited

Loading

Recommend to always label the functions with the strictest volatility #255

Recommend to always label the functions with the strictest volatility #255

Comments

steve-chavez commented Sep 18, 2019 • edited Loading

steve-chavez commented Sep 18, 2019 •

edited

Loading