From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-docs(at)postgresql(dot)org" <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Suggest adding reference to pg_db_role_setting in chapter 18; expand catalog page |
Date: | 2015-02-01 02:30:46 |
Message-ID: | 54CD8FD6.4060306@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 1/17/15 1:08 AM, David Johnston wrote:
> Attached is a patch that provides a link to the catalog page for
> pg_db_role_settings from config.sgml. It also updates said catalog page
> to mention that the data from this catalog is available via psql \drds
> and also provides a query that will explode the setconfig column into
> its component parts - which \drds does not do.
I don't like different parts of the system fighting each other about
what is better. If the exploded view is better, then we should change
\drds to show it.
> I am imagine there might be a reason that the catalog pages do not
> reference the relevant psql meta-commands, or provide human-friendly
> examples, but I cannot think of what that might be and so here I provide.
The catalog descriptions are in the "internals" part, so you'd only
arrive there if you know what you are doing. If you want to learn about
user-facing tools such as psql or pgadmin, they have their own
documentation.
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2015-02-06 05:52:54 | [PATCH] Advise devs to prefer server_version_num over parsing the version |
Previous Message | Kevin Grittner | 2015-01-26 16:11:10 | Re: how do I suggest a small docs change? |