>>> I was considering adding this and the stuff Andreas requested to
>>> pg_settings (but not "SHOW ALL" or "SHOW x" unless people feel it's
>>> important to kept them consistent with pg_settings). Were the Red Hat
>>> guys going to do this?
>>
>> pg_settings would be fine for phpPgAdmin.
>>
>
Christopher Kings-Lynne wrote:
I was considering adding this and the stuff Andreas requested to
pg_settings (but not "SHOW ALL" or "SHOW x" unless people feel it's
important to kept them consistent with pg_settings). Were the Red Hat
guys going to do this?
pg_settings would be fine for php
> I was considering adding this and the stuff Andreas requested to
> pg_settings (but not "SHOW ALL" or "SHOW x" unless people feel it's
> important to kept them consistent with pg_settings). Were the Red Hat
> guys going to do this?
pg_settings would be fine for phpPgAdmin.
Chris
--
Christopher Kings-Lynne wrote:
See my followup. Which bits of info would you like to see added that
SHOW doesn't reveal?
Unlike andreas, I'm not interested in the types and ranges of values, what I
need to know is the GUC variables that the user is allowed to set, in
particular what they can ALTER
> See my followup. Which bits of info would you like to see added that
> SHOW doesn't reveal?
Unlike andreas, I'm not interested in the types and ranges of values, what I
need to know is the GUC variables that the user is allowed to set, in
particular what they can ALTER USER / SET ... so that I
Andreas Pflug wrote:
I'd like to have type (bool/numeric/alpha/value list), min, max and
values in pg_settings.
Currently, you can select the name from a combobox, but type any value
you like, waiting for the backend to complain (or accept).
Additionally, it should be marked which vars are lega
Tom Lane wrote:
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
SHOW ALL;
Will help, but won't tell the whole story...
See my followup. Which bits of info would you like to see added that
SHOW doesn't reveal?
I'd like to have type (bool/numeric/alpha/value list), min, max and
"Christopher Kings-Lynne" <[EMAIL PROTECTED]> writes:
> SHOW ALL;
> Will help, but won't tell the whole story...
See my followup. Which bits of info would you like to see added that
SHOW doesn't reveal?
regards, tom lane
---(end of broadcast)
> I wonder if there's a way to read all allowed user/database variables
> that can be set/reset.
> I'd like to have this self-configured in pgAdmin3 instead of hard-coded.
You know, I was just about to ask this for phpPgAdmin3!!!
SHOW ALL;
Will help, but won't tell the whole story...
Chris
-
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
Andreas Pflug <[EMAIL PROTECTED]> writes:
> I wonder if there's a way to read all allowed user/database variables
> that can be set/reset.
> I'd like to have this self-configured in pgAdmin3 instead of hard-coded.
Look at SHOW ALL, maybe? Or the pg_settings system view?
If you're willing to thi
I wonder if there's a way to read all allowed user/database variables
that can be set/reset.
I'd like to have this self-configured in pgAdmin3 instead of hard-coded.
Can you give a hint?
Regards,
Andreas
---(end of broadcast)---
TIP 2: you can get
12 matches
Mail list logo
