pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL9_6_

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL_11_

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL9_5_

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL_10_

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- master

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL_12_

pgsql: docs: improve description of how to handle multiple databases

docs: improve description of how to handle multiple databases This is a redesign of the intro to the managing databases chapter. Discussion: https://postgr.es/m/[email protected] Author: David G. Johnston Backpatch-through: 9.5 Branch -- REL_13_

pgsql: docs: add COMMENT examples for new features, rename rtree

docs: add COMMENT examples for new features, rename rtree Reported-by: Jürgen Purtz Discussion: https://postgr.es/m/[email protected] Author: Jürgen Purtz Backpatch-through: 11 Branch -- REL_13_STABLE Details --- https://git.postgresql.org/pg/commitdiff/35

pgsql: docs: add COMMENT examples for new features, rename rtree

docs: add COMMENT examples for new features, rename rtree Reported-by: Jürgen Purtz Discussion: https://postgr.es/m/[email protected] Author: Jürgen Purtz Backpatch-through: 11 Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1e

pgsql: docs: add COMMENT examples for new features, rename rtree

docs: add COMMENT examples for new features, rename rtree Reported-by: Jürgen Purtz Discussion: https://postgr.es/m/[email protected] Author: Jürgen Purtz Backpatch-through: 11 Branch -- REL_12_STABLE Details --- https://git.postgresql.org/pg/commitdiff/90

pgsql: docs: add COMMENT examples for new features, rename rtree

docs: add COMMENT examples for new features, rename rtree Reported-by: Jürgen Purtz Discussion: https://postgr.es/m/[email protected] Author: Jürgen Purtz Backpatch-through: 11 Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/bfd78c0b4

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix handling of CREATE TABLE LIKE with inheritance.

Fix handling of CREATE TABLE LIKE with inheritance. If a CREATE TABLE command uses both LIKE and traditional inheritance, Vars in CHECK constraints and expression indexes that are absorbed from a LIKE parent table tended to get mis-numbered, resulting in wrong answers and/or bizarre error messages

pgsql: Fix explain regression test failure.

Fix explain regression test failure. Commit 9d701e624f caused the regression test for EXPLAIN to fail on the buildfarm member prion. This happened because of instability of test output, i.e., in text format, whether "Planning:" line is output varies depending on the system state. This commit upda

pgsql: Fix explain regression test failure.

Fix explain regression test failure. Commit 9d701e624f caused the regression test for EXPLAIN to fail on the buildfarm member prion. This happened because of instability of test output, i.e., in text format, whether "Planning:" line is output varies depending on the system state. This commit upda

pgsql: Rework EXPLAIN for planner's buffer usage.

Rework EXPLAIN for planner's buffer usage. Commit ce77abe63c allowed EXPLAIN (BUFFERS) to report the information on buffer usage during planning phase. However three issues were reported regarding this feature. (1) Previously, EXPLAIN option BUFFERS required ANALYZE. So the query had to be ac

pgsql: Rework EXPLAIN for planner's buffer usage.

Rework EXPLAIN for planner's buffer usage. Commit ce77abe63c allowed EXPLAIN (BUFFERS) to report the information on buffer usage during planning phase. However three issues were reported regarding this feature. (1) Previously, EXPLAIN option BUFFERS required ANALYZE. So the query had to be ac