Re: First SVG graphic

2019-01-17 Thread Tatsuo Ishii
>> Thanks to an additional template created by Alexander Lakhin, which extends >> the >> 'nochunk' stylesheet for SVG and MathML processing, it is now possible to >> create the "single HTML file" of our documentation including SVG. For me this >> is a working solution as long as we use Docbook 4.

Re: First SVG graphic

2019-01-17 Thread Bruce Momjian
On Thu, Jan 17, 2019 at 02:49:48PM -0300, Alvaro Herrera wrote: > On 2018-Dec-23, Jürgen Purtz wrote: > > > b) Is it worth to visualize PG's tree-implementation in a separate graphic - > > or is it the same as in every other tree-implementation that you have > > learned in your academic studies? I

Re: First SVG graphic

2019-01-17 Thread Alvaro Herrera
On 2018-Dec-23, Jürgen Purtz wrote: > b) Is it worth to visualize PG's tree-implementation in a separate graphic - > or is it the same as in every other tree-implementation that you have > learned in your academic studies? If yes: in which chapter? Who's to say that every single reader of the PG

Re: First SVG graphic

2019-01-17 Thread Bruce Momjian
On Mon, Jan 7, 2019 at 05:44:07PM +, Jürgen Purtz wrote: > My questions to the community are: > > □ Does anyone has an idea how to generate single HTML file in the actual > situation? > > > Thanks to an additional template created by Alexander Lakhin, which extends > the

Re: First SVG graphic

2019-01-17 Thread Bruce Momjian
On Sun, Dec 23, 2018 at 04:10:30PM +0100, Jürgen Purtz wrote: > a) The "Entry tree" and the "Posting trees" of the graphic "gin.svg" shows > links not only from one tree-level to the next but also within each level > from node to node. Is that correct? > > b) Is it worth to visualize PG's tree-imp

Re: Bug reporting guidelines order of instructions

2019-01-17 Thread Alvaro Herrera
On 2019-Jan-17, Magnus Hagander wrote: > Per the docs comment today, I will remove the notes about majordomo at > https://www.postgresql.org/docs/current/bug-reporting.html. > > However, this one also suggests email to the pgsql-bugs report as the > primary choice "and you can also use the bugs f

Bug reporting guidelines order of instructions

2019-01-17 Thread Magnus Hagander
Per the docs comment today, I will remove the notes about majordomo at https://www.postgresql.org/docs/current/bug-reporting.html. However, this one also suggests email to the pgsql-bugs report as the primary choice "and you can also use the bugs form. Do we perhaps want to change the order of the

Re: majord...@postgresql.org: unknown address

2019-01-17 Thread Magnus Hagander
On Thu, Jan 17, 2019 at 11:15 AM PG Doc comments form < nore...@postgresql.org> wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/bug-reporting.html > Description: > > Hi, > > https://www.postgresql.org/docs/10/bug-reporting.h

majord...@postgresql.org: unknown address

2019-01-17 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/10/bug-reporting.html Description: Hi, https://www.postgresql.org/docs/10/bug-reporting.html says "For more information send mail to with the single word help in the body of the message.".

Ambiguous description for "Index Storage Parameters" section for Create index chapter

2019-01-17 Thread PG Doc comments form
The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/11/sql-createindex.html Description: Link https://www.postgresql.org/docs/current/sql-createindex.html 1. The first paragraph contains in the third sentence an index methods list - "... The B