[COMMITTERS] pgsql: Fix ordering in pg_dump of GRANTs

[Stephen Frost]

Fix ordering in pg_dump of GRANTs

The order in which GRANTs are output is important as GRANTs which have
been GRANT'd by individuals via WITH GRANT OPTION GRANTs have to come
after the GRANT which included the WITH GRANT OPTION.  This happens
naturally in the backend during normal operation as we only change
existing ACLs in-place, only add new ACLs to the end, and when removing
an ACL we remove any which depend on it also.

Also, adjust the comments in acl.h to make this clear.

Unfortunately, the updates to pg_dump to handle initial privileges
involved pulling apart ACLs and then combining them back together and
could end up putting them back together in an invalid order, leading to
dumps which wouldn't restore.

Fix this by adjusting the queries used by pg_dump to ensure that the
ACLs are rebuilt in the same order in which they were originally.

Back-patch to 9.6 where the changes for initial privileges were done.

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/d2e40b310aea1050fd499f62f391329f2c331f6a

Modified Files
--
src/bin/pg_dump/dumputils.c | 51 -
src/include/utils/acl.h | 14 ++---
2 files changed, 47 insertions(+), 18 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Fix ordering in pg_dump of GRANTs

[Stephen Frost]

Fix ordering in pg_dump of GRANTs

The order in which GRANTs are output is important as GRANTs which have
been GRANT'd by individuals via WITH GRANT OPTION GRANTs have to come
after the GRANT which included the WITH GRANT OPTION.  This happens
naturally in the backend during normal operation as we only change
existing ACLs in-place, only add new ACLs to the end, and when removing
an ACL we remove any which depend on it also.

Also, adjust the comments in acl.h to make this clear.

Unfortunately, the updates to pg_dump to handle initial privileges
involved pulling apart ACLs and then combining them back together and
could end up putting them back together in an invalid order, leading to
dumps which wouldn't restore.

Fix this by adjusting the queries used by pg_dump to ensure that the
ACLs are rebuilt in the same order in which they were originally.

Back-patch to 9.6 where the changes for initial privileges were done.

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/68a7c24fdf2d69fc57cfb26aba7e119aa6ca2621

Modified Files
--
src/bin/pg_dump/dumputils.c | 51 -
src/include/utils/acl.h | 14 ++---
2 files changed, 47 insertions(+), 18 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Fix ordering in pg_dump of GRANTs

[Stephen Frost]

Fix ordering in pg_dump of GRANTs

The order in which GRANTs are output is important as GRANTs which have
been GRANT'd by individuals via WITH GRANT OPTION GRANTs have to come
after the GRANT which included the WITH GRANT OPTION.  This happens
naturally in the backend during normal operation as we only change
existing ACLs in-place, only add new ACLs to the end, and when removing
an ACL we remove any which depend on it also.

Also, adjust the comments in acl.h to make this clear.

Unfortunately, the updates to pg_dump to handle initial privileges
involved pulling apart ACLs and then combining them back together and
could end up putting them back together in an invalid order, leading to
dumps which wouldn't restore.

Fix this by adjusting the queries used by pg_dump to ensure that the
ACLs are rebuilt in the same order in which they were originally.

Back-patch to 9.6 where the changes for initial privileges were done.

Branch
--
REL9_6_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/caae416aac83db7c96695c1927a254e82f7da5dc

Modified Files
--
src/bin/pg_dump/dumputils.c | 51 -
src/include/utils/acl.h | 14 ++---
2 files changed, 47 insertions(+), 18 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

Re: [COMMITTERS] pgsql: Changed order of statements and added an additiona MSVC safeguar

[Michael Meskes]

> Now that some buildfarm owners have enabled ecpg tests on their Windows
> machines, it'd be a good idea to back-patch this.  I see that woodlouse
> is consistently succeeding on the master branch, but v10 not so much,
> and this commit is the only plausible reason why.

Done for 9.6 and 10. There were some other changes to the regressions
tests for 9.6, so the patches in question do not apply cleanly in 9.5
and earlier and I kind of doubt that it's worth the effort to manually
backport.

Michael

P.S.: I'm traveling, if something goes red because of this commit, feel
free to fix. :)
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Make setlocale in ECPG test cases thread aware on Windows.

[Michael Meskes]

Make setlocale in ECPG test cases thread aware on Windows.

Fix threaded test cases on Windows not to crash in setlocale() which can be
global or local to a thread on Windows.

Author: Christian Ullrich

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/38d7cb67f2e8798d6e0ecff8334345a3ae73b902

Modified Files
--
src/interfaces/ecpg/test/expected/thread-alloc.c   | 39 +++--
.../ecpg/test/expected/thread-descriptor.c | 19 +++---
src/interfaces/ecpg/test/expected/thread-prep.c| 67 --
src/interfaces/ecpg/test/expected/thread-thread.c  | 60 ++-
.../ecpg/test/expected/thread-thread_implicit.c| 60 ++-
src/interfaces/ecpg/test/thread/alloc.pgc  |  5 ++
src/interfaces/ecpg/test/thread/descriptor.pgc |  5 ++
src/interfaces/ecpg/test/thread/prep.pgc   |  5 ++
src/interfaces/ecpg/test/thread/thread.pgc |  6 ++
.../ecpg/test/thread/thread_implicit.pgc   |  6 ++
10 files changed, 163 insertions(+), 109 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Changed order of statements and added an additiona MSVC safeguar

[Michael Meskes]

Changed order of statements and added an additiona MSVC safeguard to make ecpg
thread test cases work on Windows.

Branch
--
REL9_6_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/407e660781b8c3866fe97fd5e326a078f549db61

Modified Files
--
src/interfaces/ecpg/test/expected/thread-alloc.c   | 36 ++--
.../ecpg/test/expected/thread-descriptor.c | 10 ++--
src/interfaces/ecpg/test/expected/thread-prep.c| 64 +++---
src/interfaces/ecpg/test/expected/thread-thread.c  | 38 +++--
.../ecpg/test/expected/thread-thread_implicit.c| 38 +++--
src/interfaces/ecpg/test/thread/alloc.pgc  | 10 ++--
src/interfaces/ecpg/test/thread/descriptor.pgc |  2 +
src/interfaces/ecpg/test/thread/prep.pgc   | 10 ++--
src/interfaces/ecpg/test/thread/thread.pgc | 10 ++--
.../ecpg/test/thread/thread_implicit.pgc   | 10 ++--
10 files changed, 124 insertions(+), 104 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Changed order of statements and added an additiona MSVC safeguar

[Michael Meskes]

Changed order of statements and added an additiona MSVC safeguard to make ecpg
thread test cases work on Windows.

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/eaf7001eb7e3eecc7e30c31956860f54f1def55f

Modified Files
--
src/interfaces/ecpg/test/expected/thread-alloc.c   | 36 ++--
.../ecpg/test/expected/thread-descriptor.c | 10 ++--
src/interfaces/ecpg/test/expected/thread-prep.c| 64 +++---
src/interfaces/ecpg/test/expected/thread-thread.c  | 38 +++--
.../ecpg/test/expected/thread-thread_implicit.c| 38 +++--
src/interfaces/ecpg/test/thread/alloc.pgc  | 10 ++--
src/interfaces/ecpg/test/thread/descriptor.pgc |  2 +
src/interfaces/ecpg/test/thread/prep.pgc   | 10 ++--
src/interfaces/ecpg/test/thread/thread.pgc | 10 ++--
.../ecpg/test/thread/thread_implicit.pgc   | 10 ++--
10 files changed, 124 insertions(+), 104 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Make setlocale in ECPG test cases thread aware on Windows.

[Michael Meskes]

Make setlocale in ECPG test cases thread aware on Windows.

Fix threaded test cases on Windows not to crash in setlocale() which can be
global or local to a thread on Windows.

Author: Christian Ullrich

Branch
--
REL9_6_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/839ee1811d053da4cdd0a44aea8fe7b011284be2

Modified Files
--
src/interfaces/ecpg/test/expected/thread-alloc.c   | 39 +++--
.../ecpg/test/expected/thread-descriptor.c | 19 +++---
src/interfaces/ecpg/test/expected/thread-prep.c| 67 --
src/interfaces/ecpg/test/expected/thread-thread.c  | 60 ++-
.../ecpg/test/expected/thread-thread_implicit.c| 60 ++-
src/interfaces/ecpg/test/thread/alloc.pgc  |  5 ++
src/interfaces/ecpg/test/thread/descriptor.pgc |  5 ++
src/interfaces/ecpg/test/thread/prep.pgc   |  5 ++
src/interfaces/ecpg/test/thread/thread.pgc |  6 ++
.../ecpg/test/thread/thread_implicit.pgc   |  6 ++
10 files changed, 163 insertions(+), 109 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Adjust unstable regression test case.

[Tom Lane]

Adjust unstable regression test case.

Test queries added by commit 69835bc89 are giving unexpected results
on some smaller buildfarm critters.  I think probably the seqscan
logic is kicking in to cause the scans to not start at the beginning
of the table.  Add ORDER BY to make them be indexscans instead.

Per buildfarm member chipmunk.

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/76e134fefd7de0554536e1b8d45a1878f96cf9c0

Modified Files
--
src/test/regress/expected/psql.out | 18 +++---
src/test/regress/sql/psql.sql  |  6 +++---
2 files changed, 18 insertions(+), 6 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Update contrib/seg for new scalarlesel/scalargesel selectivity f

[Tom Lane]

Update contrib/seg for new scalarlesel/scalargesel selectivity functions.

I somehow missed this module in commit 7d08ce286.

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/44ba2920644903d7dfceda810e5facdbcbab58a8

Modified Files
--
contrib/seg/Makefile  |  3 ++-
contrib/seg/seg--1.1--1.2.sql | 14 ++
contrib/seg/seg.control   |  2 +-
3 files changed, 17 insertions(+), 2 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Distinguish selectivity of < from <= and > from >=.

[Tom Lane]

Distinguish selectivity of < from <= and > from >=.

Historically, the selectivity functions have simply not distinguished
< from <=, or > from >=, arguing that the fraction of the population that
satisfies the "=" aspect can be considered to be vanishingly small, if the
comparison value isn't any of the most-common-values for the variable.
(If it is, the code path that executes the operator against each MCV will
take care of things properly.)  But that isn't really true unless we're
dealing with a continuum of variable values, and in practice we seldom are.
If "x = const" would estimate a nonzero number of rows for a given const
value, then it follows that we ought to estimate different numbers of rows
for "x < const" and "x <= const", even if the const is not one of the MCVs.
Handling this more honestly makes a significant difference in edge cases,
such as the estimate for a tight range (x BETWEEN y AND z where y and z
are close together).

Hence, split scalarltsel into scalarltsel/scalarlesel, and similarly
split scalargtsel into scalargtsel/scalargesel.  Adjust <= and >=
operator definitions to reference the new selectivity functions.
Improve the core ineq_histogram_selectivity() function to make a
correction for equality.  (Along the way, I learned quite a bit about
exactly why that function gives good answers, which I tried to memorialize
in improved comments.)

The corresponding join selectivity functions were, and remain, just stubs.
But I chose to split them similarly, to avoid confusion and to prevent the
need for doing this exercise again if someone ever makes them less stubby.

In passing, change ineq_histogram_selectivity's clamp for extreme
probability estimates so that it varies depending on the histogram
size, instead of being hardwired at 0.0001.  With the default histogram
size of 100 entries, you still get the old clamp value, but bigger
histograms should allow us to put more faith in edge values.

Tom Lane, reviewed by Aleksander Alekseev and Kuntal Ghosh

Discussion: https://postgr.es/m/12232.1499140...@sss.pgh.pa.us

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/7d08ce286cd5854d58152e428c28636a616bdc42

Modified Files
--
contrib/citext/Makefile|   3 +-
contrib/citext/citext--1.4--1.5.sql|  14 ++
contrib/citext/citext.control  |   2 +-
contrib/cube/Makefile  |   3 +-
contrib/cube/cube--1.2--1.3.sql|  12 ++
contrib/cube/cube.control  |   2 +-
contrib/hstore/Makefile|   3 +-
contrib/hstore/hstore--1.4--1.5.sql|  14 ++
contrib/hstore/hstore.control  |   2 +-
contrib/isn/Makefile   |   3 +-
contrib/isn/isn--1.1--1.2.sql  | 228 +++
contrib/isn/isn.control|   2 +-
doc/src/sgml/xindex.sgml   |   3 +-
doc/src/sgml/xoper.sgml|  35 ++--
src/backend/optimizer/path/clausesel.c |  14 +-
src/backend/utils/adt/network.c|   4 +-
src/backend/utils/adt/selfuncs.c   | 323 +
src/include/catalog/catversion.h   |   2 +-
src/include/catalog/pg_operator.h  | 224 +++
src/include/catalog/pg_proc.h  |   9 +
src/tutorial/complex.source|   4 +-
21 files changed, 633 insertions(+), 273 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: doc: Remove incorrect SCRAM protocol documentation

[Peter Eisentraut]

doc: Remove incorrect SCRAM protocol documentation

The documentation claimed that one should send
"pg_same_as_startup_message" as the user name in the SCRAM messages, but
this did not match the actual implementation, so remove it.

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/d587813edba16ae52330c881c27e4c91799a0d9c

Modified Files
--
doc/src/sgml/protocol.sgml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: doc: Remove incorrect SCRAM protocol documentation

[Peter Eisentraut]

doc: Remove incorrect SCRAM protocol documentation

The documentation claimed that one should send
"pg_same_as_startup_message" as the user name in the SCRAM messages, but
this did not match the actual implementation, so remove it.

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/089880ba9af5f95e1a3b050874a90dbe5c33fd61

Modified Files
--
doc/src/sgml/protocol.sgml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps

[Bruce Momjian]

docs:  adjust "link mode" mention in pg_upgrade streaming steps

Backpatch-through: 9.5

Branch
--
REL9_6_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/e5c8d43abde8cbb4b7fbbb5a215e497f11bf6fe6

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps

[Bruce Momjian]

docs:  adjust "link mode" mention in pg_upgrade streaming steps

Backpatch-through: 9.5

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/6dffdcfeef934eb21b8a767d8be11ec33ccb56ed

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps

[Bruce Momjian]

docs:  adjust "link mode" mention in pg_upgrade streaming steps

Backpatch-through: 9.5

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/82e367ddbfdf798ea8a30da15db3984017277342

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: adjust "link mode" mention in pg_upgrade streaming steps

[Bruce Momjian]

docs:  adjust "link mode" mention in pg_upgrade streaming steps

Backpatch-through: 9.5

Branch
--
REL9_5_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/e1795efcbecdcb53d3910cd46a067a1e66ab0938

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions

[Bruce Momjian]

docs:  improve pg_upgrade standby instructions

This makes it clear that pg_upgrade standby upgrade instructions should
only be used in link mode, adds examples, and explains how rsync works
with links.

Reported-by: Andreas Joseph Krogh

Discussion: 
https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena

Backpatch-through: 9.5

Branch
--
REL9_5_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/213409c6a3ed9d8976985b76f51822c32a710691

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 64 ++---
1 file changed, 41 insertions(+), 23 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions

[Bruce Momjian]

docs:  improve pg_upgrade standby instructions

This makes it clear that pg_upgrade standby upgrade instructions should
only be used in link mode, adds examples, and explains how rsync works
with links.

Reported-by: Andreas Joseph Krogh

Discussion: 
https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena

Backpatch-through: 9.5

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/aaa4faa7a00cb85322e570f2d148a51b95b847c4

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 64 ++---
1 file changed, 41 insertions(+), 23 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions

[Bruce Momjian]

docs:  improve pg_upgrade standby instructions

This makes it clear that pg_upgrade standby upgrade instructions should
only be used in link mode, adds examples, and explains how rsync works
with links.

Reported-by: Andreas Joseph Krogh

Discussion: 
https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena

Backpatch-through: 9.5

Branch
--
REL9_6_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/3b3327ef2762bf6753ccd5bee75a4935a09bd0a1

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 64 ++---
1 file changed, 41 insertions(+), 23 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: docs: improve pg_upgrade standby instructions

[Bruce Momjian]

docs:  improve pg_upgrade standby instructions

This makes it clear that pg_upgrade standby upgrade instructions should
only be used in link mode, adds examples, and explains how rsync works
with links.

Reported-by: Andreas Joseph Krogh

Discussion: 
https://postgr.es/m/VisenaEmail.6c.c0e592c5af4ef0a2.15e785dcb61@tc7-visena

Backpatch-through: 9.5

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/9521ce4a7a1125385fb4de9689f345db594c516a

Modified Files
--
doc/src/sgml/ref/pgupgrade.sgml | 64 ++---
1 file changed, 41 insertions(+), 23 deletions(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Improve error message in WAL sender

[Peter Eisentraut]

Improve error message in WAL sender

The previous error message when attempting to run a general SQL command
in a physical replication WAL sender was a bit sloppy.

Reported-by: Fujii Masao 

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/61975d6c2cf5bbcf40a2e3160914ecad7a21df1a

Modified Files
--
src/backend/replication/walsender.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Improve error message in WAL sender

[Peter Eisentraut]

Improve error message in WAL sender

The previous error message when attempting to run a general SQL command
in a physical replication WAL sender was a bit sloppy.

Reported-by: Fujii Masao 

Branch
--
REL_10_STABLE

Details
---
https://git.postgresql.org/pg/commitdiff/2b0ded5060cc2e0b7d6c765af5b5f7334f64f5dc

Modified Files
--
src/backend/replication/walsender.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers

[COMMITTERS] pgsql: Define LDAP_NO_ATTRS if necessary.

[Peter Eisentraut]

Define LDAP_NO_ATTRS if necessary.

Commit 83aaac41c66959a3ebaec7daadc4885b5f98f561 introduced the use of
LDAP_NO_ATTRS to avoid requesting a dummy attribute when doing search+bind
LDAP authentication.  It turns out that not all LDAP implementations define
that macro, but its value is fixed by the protocol so we can define it
ourselves if it's missing.

Author: Thomas Munro
Reported-By: Ashutosh Sharma
Discussion: 
https://postgr.es/m/CAE9k0Pm6FKCfPCiAr26-L_SMGOA7dT_k0%2B3pEbB8%2B-oT39xRpw%40mail.gmail.com

Branch
--
master

Details
---
https://git.postgresql.org/pg/commitdiff/1a2fdc99a4b341feb6c01304e58f01dd0e095d9a

Modified Files
--
src/backend/libpq/auth.c | 5 +
1 file changed, 5 insertions(+)


-- 
Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-committers