Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-05 Thread Tomas Vondra
On 5.12.2011 00:06, Tom Lane wrote: > Tomas Vondra writes: >> On 4.12.2011 22:16, Tom Lane wrote: >>> Um ... why would you design it like that? > >> The backends are added to pg_stat_activity after the auth hook finishes, >> which means possible race conditions (backends executed at about the >>

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-04 Thread Tomas Vondra
On 5.12.2011 00:06, Tom Lane wrote: > Tomas Vondra writes: >> On 4.12.2011 22:16, Tom Lane wrote: >>> Um ... why would you design it like that? > >> The backends are added to pg_stat_activity after the auth hook finishes, >> which means possible race conditions (backends executed at about the >>

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-04 Thread Tom Lane
Tomas Vondra writes: > On 4.12.2011 22:16, Tom Lane wrote: >> Um ... why would you design it like that? > The backends are added to pg_stat_activity after the auth hook finishes, > which means possible race conditions (backends executed at about the > same time don't see each other in pg_stat_act

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-04 Thread Tomas Vondra
On 4.12.2011 22:16, Tom Lane wrote: > Tomas Vondra writes: >> On 3.12.2011 18:53, Tom Lane wrote: >>> Security: it lets the DBA constrain which libraries are loadable this way. > >> But local_preload_libraries can be set only in postgresql.conf, right? > > No. It's PGC_BACKEND, which means it c

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-04 Thread Tom Lane
Tomas Vondra writes: > On 3.12.2011 18:53, Tom Lane wrote: >> Security: it lets the DBA constrain which libraries are loadable this way. > But local_preload_libraries can be set only in postgresql.conf, right? No. It's PGC_BACKEND, which means it can be set at connection start by a client (eg,

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-03 Thread Tomas Vondra
On 3.12.2011 18:53, Tom Lane wrote: > Tomas Vondra writes: >> why the libraries loaded using local_preload_libraries need to be placed >> in a different subdirectory than libraries loaded using >> shared_preload_libraries? > > Security: it lets the DBA constrain which libraries are loadable this w

Re: [HACKERS] why local_preload_libraries does require a separate directory ?

2011-12-03 Thread Tom Lane
Tomas Vondra writes: > why the libraries loaded using local_preload_libraries need to be placed > in a different subdirectory than libraries loaded using > shared_preload_libraries? Security: it lets the DBA constrain which libraries are loadable this way. > I do understand that leaving the user