| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Fernando Nasser <fnasser(at)redhat(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)redhat(dot)com>, Aizaz Ahmed <aahmed(at)redhat(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_guc |
| Date: | 2003-06-26 17:57:23 |
| Message-ID: | 200306261057.24159.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Fernando,
> We have a server side GUI utility that among other things let us configure
GUC
> variables. We badly need to know what variables exist in the specific
backend
> version, which are the min and max values and if possible a description.
The
> option is to hardwire these things into the code which is very awkward (and
we
> want it to work with different backend versions, backends compiled
differently
> etc.).
As the new "GUC List" guru, I will send you a list in PDF or SXW format
which covers 7.3 and 7.4 this weekend. If you database it, I would love to
have the table back in return.
Please note that the actual maximum value for many variables is much larger
than the practical maximum value. For example, RANDOM_PAGE_COST is only
limited to INT MAX on the host OS, even though all practical values are
between 1 and 10.
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2003-06-26 18:04:23 | Re: row description for domain in 7.4 |
| Previous Message | Paul Ramsey | 2003-06-26 17:55:28 | Re: [GENERAL] pg_dump "all tables" in 7.3.X |