Re: Doc patch: add RECURSIVE to bookindex

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Daniel Verite <daniel(at)manitou-mail(dot)org>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Doc patch: add RECURSIVE to bookindex
Date: 2018-07-31 19:11:50
Message-ID: alpine.DEB.2.21.1807311504290.6919@lancre
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

>> 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.


Patch applies cleanly, doc build ok, works for me.


In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2018-07-31 19:11:52 Re: [HACKERS] Restricting maximum keep segments by repslots
Previous Message Fabien COELHO 2018-07-31 19:02:36 Re: Usability fail with psql's \dp command