[DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

2017-10-19 Thread hoanguyen2708 
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/transaction-iso.html
Description:

In section "13.2.1. Read Committed Isolation Level" the document 
states that
"it never sees either uncommitted data or changes committed during query
execution by concurrent transactions" but this is exactly the same as
"Repeatable Read Isolation Level". Also in the last sentence of the
paragraph it says "if other transactions commit changes after the first
SELECT starts and before the second SELECT starts" meaning that it could 
see
the commited data from other concurrent transaction which is completely
contradict with the previous statement.

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] clarify 43.7

2017-10-19 Thread bderstin 
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/9.0/static/plpython-database.html
Description:

https://www.postgresql.org/docs/9.4/static/plpython-database.html

"If my_table has a column my_column, it would be accessed as:
foo = rv[i]["my_column"]
The number of rows returned can be obtained using the built-in len
function."

It it unclear where 'i' comes from or how it would be used in context. 
Also, the 'len' function is mentioned but no example is shown regarding 
how
to use it. Is there a generic way to access the entire column 
"my_column" in
foo without using 'i'? 

Is the resulting variable 'foo' a list or dictionary?

thanks!

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Typo in word "password"

2017-10-19 Thread email 
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/release-10.html
Description:

"The UNENCRYPTED option is no longer supported in CREATE/ALTER USER ...
PASSSWORD."

-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

[DOCS] Incorrect link in release notes

2017-10-19 Thread M. Justin 
When reviewing the PostgreSQL 10 release notes I discovered that the
make_date() link in "E.1.3.6. Functions" incorrectly points to
https://www.postgresql.org/docs/devel/static/functions-formatting.html#functions-formatting-table
instead of
https://www.postgresql.org/docs/10/static/functions-datetime.html#functions-datetime-table
.

Re: [DOCS] Typo in word "password"

2017-10-19 Thread Magnus Hagander 
On Sun, Oct 15, 2017 at 8:21 PM,  wrote:

> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/release-10.html
> Description:
>
> "The UNENCRYPTED option is no longer supported in CREATE/ALTER USER
> ...
> PASSSWORD."
>

That's cute. Fixed.

Thanks for the report!

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

Re: [DOCS] Wrong description in "13.2.1. Read Committed Isolation Level"

2017-10-19 Thread Pantelis Theodosiou 
On Fri, Oct 13, 2017 at 12:17 PM,  wrote:

> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/10/static/transaction-iso.html
> Description:
>
> In section "13.2.1. Read Committed Isolation Level" the document
> states that
> "it never sees either uncommitted data or changes committed during
> query
> execution by concurrent transactions" but this is exactly the same as
> "Repeatable Read Isolation Level".


They are not the same. Read Committed has:
 > ... sees data committed before the *query* began; .. changes
committed during *query execution* ...

but Repeatable Read has:
 > ... sees data committed before the *transaction* began; .. changes
committed during *transaction execution* ...


> Also in the last sentence of the
> paragraph it says "if other transactions commit changes after the
> first
> SELECT starts and before the second SELECT starts" meaning that it
> could see
> the commited data from other concurrent transaction which is completely
> contradict with the previous statement.
>
> --
> Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-docs
>

Re: [DOCS] Incorrect link in release notes

2017-10-19 Thread Tom Lane 
"M. Justin"  writes:
> When reviewing the PostgreSQL 10 release notes I discovered that the
> make_date() link in "E.1.3.6. Functions" incorrectly points to
> https://www.postgresql.org/docs/devel/static/functions-formatting.html#functions-formatting-table
> instead of
> https://www.postgresql.org/docs/10/static/functions-datetime.html#functions-datetime-table

Mmm, looks like that link should have been applied to the next item
instead (to_timestamp).  Thanks for noticing!

regards, tom lane


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs

Re: [DOCS] no more SGML empty tags

2017-10-19 Thread Tom Lane 
Peter Eisentraut  writes:
> In XML, empty tags such as  are no longer allowed.  In preparation
> for converting the documentation to DocBook XML, I have committed a
> patch that expands all such empty tags.  There is also now a warning
> from onsgmls when empty tags are used.  (There is no -werror option,
> unfortunately.)

I just want to point out that this patch has more or less entirely
destroyed any hope of cleanly back-patching documentation changes.

Should we consider applying the same transformation to the back
branches?

regards, tom lane


-- 
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs