From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr> |
Cc: | "PostgreSQL Developers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Doc patch: add RECURSIVE to bookindex |
Date: | 2018-07-31 14:17:58 |
Message-ID: | e72f973c-8a66-497b-8459-6c0cef8de6d3@manitou-mail.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fabien COELHO wrote:
> Why referencing only create_view, but not delete, insert, update, select
> or select_into where RECURSIVE is also used?
>
> ISTM that at least the select page should be referenced, I'm less sure of
> the others because there it appears only in the synopsys.
Looking at other occurrences of <indexterm>, it seems
they're used quite sparingly, limiting the references to only
the pages that have the most relevant explanation for the term,
as opposed to trying to be exhaustive.
For instance, select.sgml has only three <indexterm>, and
the entries for WHERE or JOIN don't even refer to it.
ISTM that it's on purpose, to keep the index lean, and it works.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-07-31 14:24:40 | Re: Usability fail with psql's \dp command |
Previous Message | Simon Riggs | 2018-07-31 14:00:04 | Re: Standby trying "restore_command" before local WAL |