From: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: System catalog documentation chapter |
Date: | 2022-07-20 20:23:21 |
Message-ID: | CAMsGm5fr=f8DV7EBnaF2TML6+1_pwXE8zP+_w2_S3t=6yiamqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 20 Jul 2022 at 16:08, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> On Tue, Jul 19, 2022 at 01:41:44PM -0400, Bruce Momjian wrote:
> > I am going to look at moving system views that make sense into the
> > chapters where their contents are mentioned. I don't think having a
> > central list of views is really helping us because we expect the views
> > to be used in ways the system catalogs would not be.
>
> I have grouped the views by topic. What I would like to do next is to
> move these view sections to the end of relevant documentation chapters.
> Is that going to be an improvement?
Will there be a comprehensive list somewhere? Even if it just lists the
views, gives maybe a one-sentence description, and links to the relevant
chapter, I would find that helpful sometimes.
I ask because I occasionally find myself wanting a comprehensive list of
functions, and as far as I can tell it doesn't exist. I'm hoping to avoid
that situation for views.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2022-07-20 20:32:46 | Re: System catalog documentation chapter |
Previous Message | Bruce Momjian | 2022-07-20 20:07:58 | Re: System catalog documentation chapter |