Обсуждение: shared_preload_libraries
Hi all,
We are using 9.03
Having shared_preload_libraries = 'auto_explain, pg_stat_statements' set in the conf file causes some one starting up postgres to manually have to hit the enter key. Suprresing this output with pg_ctl would be the best option, but I don't it as an option(silent doesn't cut it). We have a workaround rediriecting stdout to '> /dev/null', but I was hoping for a better solution. What about permanently loading these libraries with ld.so.conf ?
~DjK
Starting PostgreSQL:
ok
postgres@system1:~> < 2011-03-31 15:01:08 EDT> LOG: loaded library "auto_explain"
< 2011-03-31 15:01:08 EDT> LOG: loaded library "pg_stat_statements"
We are using 9.03
Having shared_preload_libraries = 'auto_explain, pg_stat_statements' set in the conf file causes some one starting up postgres to manually have to hit the enter key. Suprresing this output with pg_ctl would be the best option, but I don't it as an option(silent doesn't cut it). We have a workaround rediriecting stdout to '> /dev/null', but I was hoping for a better solution. What about permanently loading these libraries with ld.so.conf ?
~DjK
Starting PostgreSQL:
ok
postgres@system1:~> < 2011-03-31 15:01:08 EDT> LOG: loaded library "auto_explain"
< 2011-03-31 15:01:08 EDT> LOG: loaded library "pg_stat_statements"
dx k9 <bitsandbytes88@hotmail.com> writes:
> Having shared_preload_libraries = 'auto_explain, pg_stat_statements'
> set in the conf file causes some one starting up postgres to manually
> have to hit the enter key.
Really? You need to explain a lot more about how you've got things set
up, because I haven't the foggiest idea how that would happen.
regards, tom lane