pgsql: doc: Improve some documentation about HA and replication

2020-10-01 Thread Michael Paquier
doc: Improve some documentation about HA and replication This clarifies some wording in the description of the options available as replication solutions. While on it, this replaces some instances of "master" with "primary", for consistency with recent changes like 9e101cf. Author: Robert Treat

pgsql: Add pg_stat_wal statistics view.

2020-10-01 Thread Fujii Masao
Add pg_stat_wal statistics view. This view shows the statistics about WAL activity. Currently it has only two columns: wal_buffers_full and stats_reset. wal_buffers_full column indicates the number of times WAL data was written to the disk because WAL buffers got full. This information is useful w

pgsql: Add block information in error context of WAL REDO apply loop

2020-10-01 Thread Michael Paquier
Add block information in error context of WAL REDO apply loop Providing this information can be useful for example when diagnosing problems related to recovery conflicts or for recovery issues without having to go through the output generated by pg_waldump to get some information about the blocks

pgsql: Put back explicit setting of replication values within TAP tests

2020-10-01 Thread Tom Lane
Put back explicit setting of replication values within TAP tests. Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than as

pgsql: Put back explicit setting of replication values within TAP tests

2020-10-01 Thread Tom Lane
Put back explicit setting of replication values within TAP tests. Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than as

pgsql: Put back explicit setting of replication values within TAP tests

2020-10-01 Thread Tom Lane
Put back explicit setting of replication values within TAP tests. Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than as

pgsql: Put back explicit setting of replication values within TAP tests

2020-10-01 Thread Tom Lane
Put back explicit setting of replication values within TAP tests. Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than as

pgsql: Put back explicit setting of replication values within TAP tests

2020-10-01 Thread Tom Lane
Put back explicit setting of replication values within TAP tests. Commit 151c0c5f7 neglected the possibility that a TEMP_CONFIG file would explicitly set max_wal_senders=0; as indeed buildfarm member thorntail does, so that it can test wal_level=minimal in other test suites. Hence, rather than as

pgsql: Fix incorrect assertion on number of array dimensions.

2020-10-01 Thread Heikki Linnakangas
Fix incorrect assertion on number of array dimensions. This has been wrong ever since the support for multi-dimensional arrays as PL/python function arguments and return values was introduced in commit 94aceed317. Backpatch-through: 10 Discussion: https://www.postgresql.org/message-id/61647b8e-9

pgsql: Fix incorrect assertion on number of array dimensions.

2020-10-01 Thread Heikki Linnakangas
Fix incorrect assertion on number of array dimensions. This has been wrong ever since the support for multi-dimensional arrays as PL/python function arguments and return values was introduced in commit 94aceed317. Backpatch-through: 10 Discussion: https://www.postgresql.org/message-id/61647b8e-9

pgsql: Fix incorrect assertion on number of array dimensions.

2020-10-01 Thread Heikki Linnakangas
Fix incorrect assertion on number of array dimensions. This has been wrong ever since the support for multi-dimensional arrays as PL/python function arguments and return values was introduced in commit 94aceed317. Backpatch-through: 10 Discussion: https://www.postgresql.org/message-id/61647b8e-9

pgsql: Fix incorrect assertion on number of array dimensions.

2020-10-01 Thread Heikki Linnakangas
Fix incorrect assertion on number of array dimensions. This has been wrong ever since the support for multi-dimensional arrays as PL/python function arguments and return values was introduced in commit 94aceed317. Backpatch-through: 10 Discussion: https://www.postgresql.org/message-id/61647b8e-9

pgsql: Fix incorrect assertion on number of array dimensions.

2020-10-01 Thread Heikki Linnakangas
Fix incorrect assertion on number of array dimensions. This has been wrong ever since the support for multi-dimensional arrays as PL/python function arguments and return values was introduced in commit 94aceed317. Backpatch-through: 10 Discussion: https://www.postgresql.org/message-id/61647b8e-9

pgsql: Set right-links during sorted GiST index build.

2020-10-01 Thread Heikki Linnakangas
Set right-links during sorted GiST index build. This is not strictly necessary, as the right-links are only needed by scans that are concurrent with page splits, and neither scans or page splits can happen during sorted index build. But it seems like a good idea to set them anyway, if we e.g. want