Consistent reference to RFCs in the documentation

2020-11-05 Thread Daniel Gustafsson
When referencing RFC's, we have a mix of ulinking to the ietf.org entry and
not.  Also, for subsequent mentions of the same RFC on the same page we have
some as  while others are not.  The attached patch adds ulinks for all
RFC's and marks subsequent mentions as acronym to make the docs consistent.  It
also spells all as "RFC " with a whitespace as that was the most
commonly used spelling (there is no RFC for how to reference to an RFC so we're
free to choose).

In order to make review easier I haven't fixed linelengths/wrapping, but am
happy to do that in case this is deemed something we want.

cheers ./daniel



0001-docs-ulink-all-references-to-RFC-s.patch
Description: Binary data


Possible Example Error in Documentation

2020-11-05 Thread PG Doc comments form
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/12/plpgsql-transactions.html
Description:

We are using Postgres 12. When I use the example given for
transaction_test1() from the documentation here:
https://www.postgresql.org/account/comments/new/12/plpgsql-transactions.html/,
the procedure is created without incident.  However, when I attempt "CALL
transaction_test1();", I receive the "invalid transaction termination"
error.

Please correct the documentation if the example is flawed, or add an
explanation on the page if we need to set specific environment variables.

Thank you.


Re: Possible Example Error in Documentation

2020-11-05 Thread Tom Lane
PG Doc comments form  writes:
> The following documentation comment has been logged on the website:
> Page: https://www.postgresql.org/docs/12/plpgsql-transactions.html
> Description:

> We are using Postgres 12. When I use the example given for
> transaction_test1() from the documentation here:
> https://www.postgresql.org/account/comments/new/12/plpgsql-transactions.html/,
> the procedure is created without incident.  However, when I attempt "CALL
> transaction_test1();", I receive the "invalid transaction termination"
> error.

Hmm, it works for me.

regards, tom lane