pgsql: meson: Add some missing env settings for tests of pg_dump and pg

2022-11-28 Thread Michael Paquier
meson: Add some missing env settings for tests of pg_dump and pg_verifybackup The commands used for the compression tests were missing in a few places, causing the tests related to these to never run. Georgios has spotted GZIP_PROGRAM missing in pg_dump, while I have noticed the ones missing in p

pgsql: Fix comment in snapbuild.c

2022-11-28 Thread Michael Paquier
Fix comment in snapbuild.c Author: Masahiko Sawada Discussion: https://postgr.es/m/cad21aoamf-pksnmgajg2dtghp7o7vphoexcxfqlkzg8xrbr...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/8aa03f3caaed9dd438a20c3423daa43a44549d60 Modified Files --

pgsql: Remove promote_trigger_file.

2022-11-28 Thread Thomas Munro
Remove promote_trigger_file. Previously, an idle startup (recovery) process would wake up every 5 seconds to have a chance to poll for promote_trigger_file, even if that GUC was not configured. That promotion triggering mechanism was effectively superseded by pg_ctl promote and pg_promote() a lon

pgsql: meson: Fix binary mismatch for MSVC plperl vs gcc built perl lib

2022-11-28 Thread Andres Freund
meson: Fix binary mismatch for MSVC plperl vs gcc built perl libs This mirrors ccc59a83cd9. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f0cd57f852cb88a4252db175317ec4627ec1b1cd Modified Files -- meson.build | 6 ++ 1 file changed, 6 insertions(+)

pgsql: Provide non-superuser predefined roles for vacuum and analyze

2022-11-28 Thread Andrew Dunstan
Provide non-superuser predefined roles for vacuum and analyze This provides two new predefined roles: pg_vacuum_all_tables and pg_analyze_all_tables. Roles which have been granted these roles can perform vacuum or analyse respectively on any or all tables as if they were a superuser. This removes

pgsql: Provide per-table permissions for vacuum and analyze.

2022-11-28 Thread Andrew Dunstan
Provide per-table permissions for vacuum and analyze. Currently a table can only be vacuumed or analyzed by its owner or a superuser. This can now be extended to any user by means of an appropriate GRANT. Nathan Bossart Reviewed by: Bharath Rupireddy, Kyotaro Horiguchi, Stephen Frost, Robert Haa

pgsql: doc: Clarify unit of logging for log_temp_files

2022-11-28 Thread Daniel Gustafsson
doc: Clarify unit of logging for log_temp_files When the unit is omitted from log_temp_files the value is taken as kb, but the logged value is also without unit but specified in bytes. This could cause some confusion, so clarify in the documentation which unit is used when logging. Reported-by: i