pgsql: doc: Change table alias names to lower case in tutorial chapter

2020-09-03 Thread Peter Eisentraut
doc: Change table alias names to lower case in tutorial chapter This is needlessly different from our usual style otherwise. Author: Jürgen Purtz Discussion: https://www.postgresql.org/message-id/flat/158996922318.7035.10603922579567326...@wrigleys.postgresql.org Branch -- master Details

pgsql: doc: Fix whitespace issue in PDF

2020-09-03 Thread Peter Eisentraut
doc: Fix whitespace issue in PDF Move outside of to avoid whitespace issue in PDF output. Author: Jürgen Purtz Discussion: https://www.postgresql.org/message-id/flat/158996922318.7035.10603922579567326...@wrigleys.postgresql.org Branch -- master Details --- https://git.postgresql.or

pgsql: doc: Use tags consistently in the tutorial chapter

2020-09-03 Thread Peter Eisentraut
doc: Use tags consistently in the tutorial chapter Make more consistent use of and . Author: Jürgen Purtz Discussion: https://www.postgresql.org/message-id/flat/158996922318.7035.10603922579567326...@wrigleys.postgresql.org Branch -- master Details --- https://git.postgresql.org/pg/c

pgsql: Remove unused parameter

2020-09-03 Thread Peter Eisentraut
Remove unused parameter unused since 93ee38eade1b2b4964354b95b01b09e17d6f098d Discussion: https://www.postgresql.org/message-id/flat/511bb100-f829-ba21-2f10-9f952ec06ead%402ndquadrant.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/96cfcadd26e26e138ae60f4f3f94

pgsql: Fix inline marking introduced in commit 464824323e.

2020-09-03 Thread Amit Kapila
Fix inline marking introduced in commit 464824323e. Forgot to add inline marking in changes_filename() declaration. In the passing, add inline marking for a similar function subxact_filename(). Reported-By: Nathan Bossart Discussion: https://postgr.es/m/e98fbe8f-b878-480d-a728-a60c6eed3...@amazo

pgsql: remove redundant initializations

2020-09-03 Thread Bruce Momjian
remove redundant initializations Reported-by: Ranier Vilela Discussion: https://postgr.es/m/CAEudQAo1+AcGppxDSg8k+zF4+Kv+eJyqzEDdbpDg58-=mqc...@mail.gmail.com Author: Ranier Vilela Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e36e936

pgsql: Remove variable "concurrent" from ReindexStmt

2020-09-03 Thread Michael Paquier
Remove variable "concurrent" from ReindexStmt This node already handles multiple options using a bitmask, so having a separate boolean flag is not necessary. This simplifies the code a bit with less arguments to give to the reindex routines, by replacing the boolean with an equivalent bitmask val

pgsql: Remove arbitrary restrictions on password length.

2020-09-03 Thread Tom Lane
Remove arbitrary restrictions on password length. This patch started out with the goal of harmonizing various arbitrary limits on password length, but after awhile a better idea emerged: let's just get rid of those fixed limits. recv_password_packet() has an arbitrary limit on the packet size, wh

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Avoid lockup of a parallel worker when reporting a long error me

2020-09-03 Thread Tom Lane
Avoid lockup of a parallel worker when reporting a long error message. Because sigsetjmp() will restore the initial state with signals blocked, the code path in bgworker.c for reporting an error and exiting would execute that way. Usually this is fairly harmless; but if a parallel worker had an e

pgsql: Allow records to span multiple lines in pg_hba.conf and pg_ident

2020-09-03 Thread Tom Lane
Allow records to span multiple lines in pg_hba.conf and pg_ident.conf. A backslash at the end of a line now causes the next line to be appended to the current one (effectively, the backslash and newline are discarded). This allows long HBA entries to be created without legibility problems. While

pgsql: Doc: mention packager-supplied tools for server start/stop, init

2020-09-03 Thread Tom Lane
Doc: mention packager-supplied tools for server start/stop, initdb, etc. The majority of our audience is probably using a pre-packaged Postgres build rather than raw sources. For them, much of runtime.sgml is not too relevant, and they should be reading the packager's docs instead. Add some notes

pgsql: Doc: mention packager-supplied tools for server start/stop, init

2020-09-03 Thread Tom Lane
Doc: mention packager-supplied tools for server start/stop, initdb, etc. The majority of our audience is probably using a pre-packaged Postgres build rather than raw sources. For them, much of runtime.sgml is not too relevant, and they should be reading the packager's docs instead. Add some notes

pgsql: doc: Make SQL command names in the catalog documentation links

2020-09-03 Thread Peter Eisentraut
doc: Make SQL command names in the catalog documentation links In passing, fix the initdb references to be rather than , which is what we normally use. Author: Dagfinn Ilmari Mannsåker Discussion: https://www.postgresql.org/message-id/flat/87mu5xqc11@wibble.ilmari.org Branch -- master

pgsql: doc: Add missing cross-links in system catalog documentation

2020-09-03 Thread Peter Eisentraut
doc: Add missing cross-links in system catalog documentation This makes the first mention of a system catalog or view in each paragraph in the system system catalog and view documentation pages hyperlinks, for easier navigation. Also linkify the first mention of pg_hba.conf in pg_hba_file_rules,

pgsql: Fix XML id to match containing page

2020-09-03 Thread Peter Eisentraut
Fix XML id to match containing page This was apparently a typo when this part of the documentation was first added. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/4220e5721a27286aab726e87d3db5d1ee475fe23 Modified Files -- doc/src/sgml/logical-replicati