pgsql: Fix grammar in documentation related to checkpoint_flush_after

Fix grammar in documentation related to checkpoint_flush_after Reported-by: Christopher Jones Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d61bfdda8c2cae671ca4a252993bb8feaa619285 Modified Files -- doc/src/sgml/wal.sgml | 4 ++-- 1 file changed, 2 ins

pgsql: Fix grammar in documentation related to checkpoint_flush_after

Fix grammar in documentation related to checkpoint_flush_after Reported-by: Christopher Jones Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/256d43128d21891b6090e6fc19668e27da04764b Modified Files -- doc/src/sgml/wal.sgml | 4 ++-- 1 file changed

pgsql: Fix grammar in documentation related to checkpoint_flush_after

Fix grammar in documentation related to checkpoint_flush_after Reported-by: Christopher Jones Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/858571843c8a5a69527faa3e57f8adfa4165 Modified Files -- doc/src/sgml/wal.sgml | 4 ++-- 1 file changed

pgsql: Fix a couple of bugs with replication slot advancing feature

Fix a couple of bugs with replication slot advancing feature A review of the code has showed up a couple of issues fixed by this commit: - Physical slots have been using the confirmed LSN position as a start comparison point which is always 0/0, instead use the restart LSN position (logical slots

pgsql: Assorted cosmetic cleanup of run-time-partition-pruning code.

Assorted cosmetic cleanup of run-time-partition-pruning code. Use "subplan" rather than "subnode" to refer to the child plans of a partitioning Append; this seems a bit more specific and hence clearer. Improve assorted comments. No non-cosmetic changes. David Rowley and Tom Lane Discussion: h

pgsql: Relocate partition pruning structs to a saner place.

Relocate partition pruning structs to a saner place. These struct definitions were originally dropped into primnodes.h, which is a poor choice since that's mainly intended for primitive expression node types; these are not in that category. What they are is auxiliary info in Plan trees, so move t

pgsql: Improve run-time partition pruning to handle any stable expressi

Improve run-time partition pruning to handle any stable expression. The initial coding of the run-time-pruning feature only coped with cases where the partition key(s) are compared to Params. That is a bit silly; we can allow it to work with any non-Var-containing stable expression, as long as we

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/6620b0faf3d18460037fe0922b7f0a355ca021d2 Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 d

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/c83e2029909c5411ca11fd841851016f1f9810e6 Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- REL9_3_STABLE Details --- https://git.postgresql.org/pg/commitdiff/50dfe3a44c65e8abf853d7bdc222002151c7046b Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 d

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/5bb08c7000db0f3f6621316105de1711f7b559a5 Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 d

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- REL9_4_STABLE Details --- https://git.postgresql.org/pg/commitdiff/25a85613b77b9c8b894be2a238ead3716f56a68c Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 d

pgsql: Fix grammar in REVOKE documentation

Fix grammar in REVOKE documentation Reported-by: Erwin Brandstetter Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/fd73508fd15937da6580bed7080ed77563e7e39f Modified Files -- doc/src/sgml/ref/revoke.sgml | 2 +- 1 file changed, 1 insertion(+), 1 d

pgsql: Fix and document lock handling for in-memory replication slot da

Fix and document lock handling for in-memory replication slot data While debugging issues on HEAD for the new slot forwarding feature of Postgres 11, some monitoring of the code surrounding in-memory slot data has proved that the lock handling may cause inconsistent data to be read by read-only ca

pgsql: Limit Parallel Hash's bucket array to MaxAllocSize.

Limit Parallel Hash's bucket array to MaxAllocSize. Make sure that we don't exceed MaxAllocSize when increasing the number of buckets. Perhaps later we'll remove that limit and use DSA_ALLOC_HUGE, but for now just prevent further increases like the non-parallel code. This change avoids the error