From: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: allowed user/db variables |
Date: | 2003-06-18 22:19:54 |
Message-ID: | 3EF0E58A.5030304@web.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tom Lane wrote:
>Look at SHOW ALL, maybe?
>
Of course.... Sorry.
>If you're willing to think about a solution that would only exist
>starting in 7.4 --- some of my cohorts at Red Hat are about to submit
>patches that create a separate "pg_guc" executable that contains
>another copy of the backend's GUC variable table, and can be used to
>obtain the set of known variables, their wired-in default values, min
>and max values, etc. So you could imagine executing this program to
>get the info. However, this would only work on the machine where the
>stuff is installed, not necessarily on a remote client, so maybe it
>wouldn't help pgAdmin.
>
No, need to retrieve this online.
Thanks,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-06-19 01:18:50 | Re: pg_get_triggerdef in pg_dump |
Previous Message | Tom Lane | 2003-06-18 22:11:40 | Re: allowed user/db variables |
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-06-19 01:28:26 | Re: allowed user/db variables |
Previous Message | Tom Lane | 2003-06-18 22:11:40 | Re: allowed user/db variables |