Yes. Although you can use the pg_config table as suggested, I prefer using
the functions provided with Postgres for this purpose. To find out
configuration settings, use the current_setting () function. It takes a
single varchar parameter: the name of the setting you are inquiring about.
E.g.,:
=> select current_setting ('search_path') ;
The complementary function as an (unfortunately) unrelated name:
set_config( config_param_na me, config_param_va lue, is_local). The is_local
boolean flag indicates whether the setting should apply only to the current
transaction or whether it should be held onto for the entire session
(connection). The "local" version only makes sense if you are inside of a
transaction block.
Example usage:
=> select set_config('sea rch_path', 'information_sc hema', false);
Note that most settings can be configured on a per-database and per-user
basis. This is recommended if you want a setting to be there everytime a
user connects or the db is started. Also, some settings (like whether to
fsync() or not) are global and can only be set in the configuration files or
on the command line at server start up.
HTH
== Ezra Epstein
"CSN" <co************ *******@yahoo.c om> wrote in message
news:20******** *************** *@web40601.mail .yahoo.com...
Is is possible to find out what options (prefix,
bindir, etc.) were specified to "configure" when
Postgres was built?
_______________ _______________ ____
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings
