pgsql: Remove superfluous semicolon.

2019-07-31 Thread Andres Freund
Remove superfluous semicolon. Author: Andres Freund Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6384e87be28ee8d69ef11e49413b115506a3c6d3 Modified Files -- src/backend/access/transam/xlogreader.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Remove superfluous newlines in function prototypes.

2019-07-31 Thread Andres Freund
Remove superfluous newlines in function prototypes. These were introduced by pgindent due to fixe to broken indentation (c.f. 8255c7a5eeba8). Previously the mis-indentation of function prototypes was creatively used to reduce indentation in a few places. As that formatting only exists in master a

pgsql: Remove superfluous newlines in function prototypes.

2019-07-31 Thread Andres Freund
Remove superfluous newlines in function prototypes. These were introduced by pgindent due to fixe to broken indentation (c.f. 8255c7a5eeba8). Previously the mis-indentation of function prototypes was creatively used to reduce indentation in a few places. As that formatting only exists in master a

pgsql: Run UTF8-requiring collation tests by default

2019-07-31 Thread Peter Eisentraut
Run UTF8-requiring collation tests by default The tests collate.icu.utf8 and collate.linux.utf8 were previously only run when explicitly selected via EXTRA_TESTS. They require a UTF8 database, because the error messages in the expected files refer to that, and they use some non-ASCII characters i

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix pg_dump's handling of dependencies for custom opclasses.

2019-07-31 Thread Tom Lane
Fix pg_dump's handling of dependencies for custom opclasses. Since pg_dump doesn't treat the member operators and functions of operator classes/families (that is, the pg_amop and pg_amproc entries, not the underlying operators/functions) as separate dumpable objects, it missed their dependency inf

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr

pgsql: Fix handling of previous password hooks in passwordcheck

2019-07-31 Thread Michael Paquier
Fix handling of previous password hooks in passwordcheck When piling up loading of modules using check_password_hook_type, loading passwordcheck would remove any trace of a previously-loaded hook. Unloading the module would also cause previous hooks to be entirely gone. Reported-by: Rafael Castr