Hello All,
I have been writing a function with SECURITY DEFINER enabled. Basically, I
am looking for ways to override the users SET option settings while
executing my function to prevent the permissions breach. For example, to
override SET search_path, I am setting search path in my function
Hello
you can overwrite standard settings only for function
CREATE [ OR REPLACE ] FUNCTION
name ( [ [ argmode ] [ argname ] argtype [ { DEFAULT | = }
default_expr ] [, ...] ] )
[ RETURNS rettype
| RETURNS TABLE ( column_name column_type [, ...] ) ]
{ LANGUAGE lang_name
|
Jignesh Shah wrote:
I have been writing a function with SECURITY DEFINER enabled.
Basically, I am looking for ways to override the users SET
option settings while executing my function to prevent the
permissions breach. For example, to override SET
search_path, I am setting search path in
Thanks a ton Laurenz and Pavel for your responses but I really didn't follow
you. I am not master in PostGreSQL yet. Could you please give me some
example?
Basically, I want to know how many such SET options I should reset before
executing my function and at the end it should also be restored to
2010/2/22 Jignesh Shah jignesh.shah1...@gmail.com:
Thanks a ton Laurenz and Pavel for your responses but I really didn't follow
you. I am not master in PostGreSQL yet. Could you please give me some
example?
Basically, I want to know how many such SET options I should reset before
executing
set work_mem to '1MB'
set search_path = 'public';
Thanks for the example Pavel. I understood it. Are there any other SET
options except above that I need to set to prevent security breach?
Thanks,
Jack
On Mon, Feb 22, 2010 at 11:41 PM, Pavel Stehule pavel.steh...@gmail.comwrote:
2010/2/22
2010/2/22 Jignesh Shah jignesh.shah1...@gmail.com:
set work_mem to '1MB'
set search_path = 'public';
Thanks for the example Pavel. I understood it. Are there any other SET
options except above that I need to set to prevent security breach?
I am not sure - I know only search_path
Pavel
