[COMMITTERS] pgsql: Remove pgbench's restriction on placement of -M switch.

Remove pgbench's restriction on placement of -M switch. Previously the -M switch had to appear before any switch that directly or indirectly specified a benchmarking script. This was both confusing and inadequately documented, as per gripe from Tatsuo Ishii. We can remove the restriction at the

[COMMITTERS] pgsql: pg_upgrade: Clarify one message

pg_upgrade: Clarify one message Reported-by: Dennis Björklund Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d4ede668d6f0ca9e5dd6def4ea1ccddc441c6073 Modified Files -- src/bin/pg_upgrade/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -

[COMMITTERS] pgsql: doc: Small wording improvement

doc: Small wording improvement Author: Jeff Janes Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/22701a7ec66ffb3b62fae7f04ef36bc6ea21df52 Modified Files -- doc/src/sgml/ref/pg_restore.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sen

[COMMITTERS] pgsql: doc: Update description of rolreplication column

doc: Update description of rolreplication column Since PostgreSQL 9.6, rolreplication no longer determines whether a role can run pg_start_backup() and pg_stop_backup(), so remove that. Add that this attribute determines whether a role can create and drop replication slots. Reported-by: Fujii Ma

[COMMITTERS] pgsql: doc: Update description of rolreplication column

doc: Update description of rolreplication column Since PostgreSQL 9.6, rolreplication no longer determines whether a role can run pg_start_backup() and pg_stop_backup(), so remove that. Add that this attribute determines whether a role can create and drop replication slots. Reported-by: Fujii Ma

[COMMITTERS] pgsql: doc: Add example for inet vs cidr difference

doc: Add example for inet vs cidr difference Reported-by: [email protected] Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/ee844bb42632521c89497a2845079770b32a934e Modified Files -- doc/src/sgml/datatype.sgml | 4 +++- 1 file changed, 3 insertions(+), 1

[COMMITTERS] pgsql: Add regression tests exercising more code paths in nodeLimit.c.

Add regression tests exercising more code paths in nodeLimit.c. Perusal of the code coverage report shows that the existing regression test cases for LIMIT/OFFSET don't exercise the nodeLimit code paths involving backwards scan, empty results, or null values of LIMIT/OFFSET. Improve the coverage.

[COMMITTERS] pgsql: Add regression tests exercising the non-hashed code paths in nod

Add regression tests exercising the non-hashed code paths in nodeSetop.c. Perusal of the code coverage report shows that the existing regression test cases for INTERSECT and EXCEPT seemingly all prefer the SETOP_HASHED implementation. Add some test cases in which we force use of the SETOP_SORTED

[COMMITTERS] pgsql: Be more thorough about cleaning out gcov litter.

Be more thorough about cleaning out gcov litter. At least on my machine, a run with code coverage enabled produces some ".gcov" files whose names begin with ".". "rm -f *.gcov" fails to match those, so they don't get cleaned up by "make clean". Fix it. Branch -- master Details --- http