From: | "Luiz K(dot) Matsumura" <luiz(at)planit(dot)com(dot)br> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Suggestion for new function on pg_catalog: get_config() |
Date: | 2007-09-04 03:05:47 |
Message-ID: | 46DCCB8B.2070105@planit.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Alvaro Herrera wrote:
> Luiz K. Matsumura wrote:
>
>> Hi all,
>>
>> I want to suggest a inclusion of an new function on the pg_catalog.
>> Since we have set_config(text, text, boolean)
>> can we have an get_config( text ) ?
>>
>
> Hum, isn't this current_setting()?
>
>
Oh oh, you are right, forget my suggestion... :-[
I'm lost in the ocean of functions of pg_catalog. lol
By the way,
select setting AS default_tablespace from pg_show_all_settings() x(name
text, setting text, unit text, category text, short_desc text,
extra_desc text, context text, vartype text, source text, min_val text,
max_val text) where name = 'default_tablespace'
and
select current_setting('default_tablespace' )
can be considered equivalent ?
I'm just researching on a bug that i found in the new pgadmin3 and if
this is equivalent i will suggest to pgadmin team to use it...
TIA
--
Luiz K. Matsumura
Plan IT Tecnologia Informática Ltda.
From | Date | Subject | |
---|---|---|---|
Next Message | Ow Mun Heng | 2007-09-04 03:31:19 | Re: Instances where enable_seqscan = false is good |
Previous Message | Alvaro Herrera | 2007-09-04 02:45:49 | Re: Suggestion for new function on pg_catalog: get_config() |