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-tree, hash, GiST and SP-GiST index methods ..."
But in text above describes just B-btree, GiST, GIN and BRIN index methods.

What is correct?
2. B-tree index additionally accept this parameter:
vacuum_cleanup_index_scale_factor
Is it so difficult to point that it is get float value and has defined
range?
Maybe this lack is cause why Toad Edge not recognized this parameter at all.
Who knows? Do you know something about this parameter? Could you type some
words about your knowledge in that chapter?
If you just copy the lastest paragraph from
https://www.postgresql.org/docs/current/runtime-config-client.html#GUC-VACUUM-CLEANUP-INDEX-SCALE-FACTOR
to this chapter it will be gorgeous.
3. The same shit (I mean lack information about legal and default values)
there is for BRIN autosummarize parameter

Probably I am not smart and could not understand from just one word. So does
good written documentation should help for everyone then?
I hope for understanding and cooperation
Thanks

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.". However sending email to this address
fails:

: host magus.postgresql.org[87.238.57.229] said:
550
unknown address (in reply to RCPT TO command)

Best,

-- 
Antoine

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.html says "For more
> information send mail to  with the single word
> help in the body of the message.". However sending email to this address
> fails:
>
> : host magus.postgresql.org[87.238.57.229] said:
> 550
> unknown address (in reply to RCPT TO command)
>
>
Hi!

That is indeed incorrect. Please go to https://lists.postgresql.org/ for
instructions on how to subscribe to it.

I will make sure the instructions are updated in the documentation.


Thanks for the report!

//Magnus

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 these and suggest the web form as the primary method,
since that hands out bug ids?

-- 
 Magnus Hagander
 Me: https://www.hagander.net/ 
 Work: https://www.redpill-linpro.com/

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 form. Do we perhaps want to
> change the order of these and suggest the web form as the primary method,
> since that hands out bug ids?

+1.

-- 
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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

I am CC'ing Oleg, Teodor, and Alexander, who can answer the first
question, and maybe the second.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

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
> '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. After the migration to
> Docbook 5, both languages as well as full namespace support will be natively
> included in Docbook.
> 
> Does anyone faced some more problems? Or can we start to include the three
> first SVG graphics into PG's documentation?

OK, the wiki pages look good, as do the diagrams, and I think you have
the process we all agreed with.  Should we move ahead and commit some of
these diagrams to the souce tree for PG 12? 

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

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 documentation has had
relevant academic studies?  My opinion is that these graphics are worth
including even if they're well-known to many.

-- 
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

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? If yes: in which chapter?
> 
> Who's to say that every single reader of the PG documentation has had
> relevant academic studies?  My opinion is that these graphics are worth
> including even if they're well-known to many.

Agreed.  Indexing methods are mysterious without diagrams.

-- 
  Bruce Momjian  http://momjian.us
  EnterpriseDB http://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+  Ancient Roman grave inscription +

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. After the migration to
>> Docbook 5, both languages as well as full namespace support will be natively
>> included in Docbook.
>> 
>> Does anyone faced some more problems? Or can we start to include the three
>> first SVG graphics into PG's documentation?
> 
> OK, the wiki pages look good, as do the diagrams, and I think you have
> the process we all agreed with.  Should we move ahead and commit some of
> these diagrams to the souce tree for PG 12? 

Yes, I think we should.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp