[COMMITTERS] pgsql: Update expected file

2017-05-25 Thread Alvaro Herrera
Update expected file Missed in ea3e310e712a. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/08aa5506948e010dacaa344074063ccd0ecc3b21 Modified Files -- src/pl/plpython/expected/plpython_ereport.out | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-

Re: [COMMITTERS] pgsql: Fix message case

2017-05-25 Thread Andres Freund
On 2017-05-25 17:16:23 +, Alvaro Herrera wrote: > Fix message case > > Branch > -- > master > > Details > --- > https://git.postgresql.org/pg/commitdiff/ea3e310e712ac53653d4100ea2a7c516c30d4971 > > Modified Files > -- > src/pl/plpython/plpy_plpymodule.c | 2 +- > 1 file ch

[COMMITTERS] pgsql: extended stats: Clarify behavior of omitting stat type clause

2017-05-25 Thread Alvaro Herrera
extended stats: Clarify behavior of omitting stat type clause Pointed out by Jeff Janes Discussion: https://postgr.es/m/CAMkU=1zGhK-nW10RAXhokcT3MM=YBg=j5lkg9rmdwmu3i0h...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/eb67e2e35a046f700172fbce52ad23

[COMMITTERS] pgsql: Fix message case

2017-05-25 Thread Alvaro Herrera
Fix message case Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/ea3e310e712ac53653d4100ea2a7c516c30d4971 Modified Files -- src/pl/plpython/plpy_plpymodule.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing lis

[COMMITTERS] pgsql: Fix whitespace

2017-05-25 Thread Peter Eisentraut
Fix whitespace Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/04f1798eaa0aeff81f90e2d28679b0a2cd267b8e Modified Files -- src/interfaces/ecpg/ecpglib/pg_type.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing l

[COMMITTERS] pgsql: Abort authentication if the client selected an invalid SASL mech

2017-05-25 Thread Heikki Linnakangas
Abort authentication if the client selected an invalid SASL mechanism. Previously, the server would log an error, but then try to continue with SCRAM-SHA-256 anyway. Michael Paquier Discussion: https://www.postgresql.org/message-id/cab7npqr0g5af2_kc_lh29knvqwvmbc66tf5dicvpgvdke68...@mail.gmail.