pgsql: Fix typo

2018-07-10 Thread Peter Eisentraut
Fix typo Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/1287c051723261ac197d3cb0d3c753b045908202 Modified Files -- config/c-compiler.m4 | 2 +- src/include/pg_config.h.in | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)

pgsql: Fix typo

2018-07-10 Thread Peter Eisentraut
Fix typo Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/8caf262097d828174c0e2dcc198a032246ed9bca Modified Files -- config/c-compiler.m4 | 2 +- src/include/pg_config.h.in | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)

pgsql: Fix typo

2018-07-10 Thread Peter Eisentraut
Fix typo Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/502120ccda205d8d2d9ad5dddac5a8a51fa8efb7 Modified Files -- config/c-compiler.m4 | 2 +- src/include/pg_config.h.in | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)

pgsql: Fix typos

2018-07-10 Thread Peter Eisentraut
Fix typos Branch -- REL_11_STABLE Details --- https://git.postgresql.org/pg/commitdiff/4cf30f6fdeed4977dfe52bf1d4fda74c883d3760 Modified Files -- config/c-compiler.m4 | 4 ++-- src/include/pg_config.h.in | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-)

pgsql: Fix typos

2018-07-10 Thread Peter Eisentraut
Fix typos Branch -- REL9_5_STABLE Details --- https://git.postgresql.org/pg/commitdiff/324c9554022d4403f34264598cb6e0a7d0d5873c Modified Files -- config/c-compiler.m4 | 4 ++-- src/include/pg_config.h.in | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-)

pgsql: Fix typos

2018-07-10 Thread Peter Eisentraut
Fix typos Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/1486f7f981c0052988891677d4e734b14317816c Modified Files -- config/c-compiler.m4 | 4 ++-- src/include/pg_config.h.in | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-)

pgsql: Fix typos

2018-07-10 Thread Peter Eisentraut
Fix typos Branch -- REL_10_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7f0911f33ece28c85e9561f7b3e4157336cfd354 Modified Files -- config/c-compiler.m4 | 4 ++-- src/include/pg_config.h.in | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-)

pgsql: Fix typos

2018-07-10 Thread Peter Eisentraut
Fix typos Branch -- REL9_6_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d93c05635f4290109ee39d95bf181543428a6977 Modified Files -- config/c-compiler.m4 | 4 ++-- src/include/pg_config.h.in | 5 +++-- 2 files changed, 5 insertions(+), 4 deletions(-)

pgsql: Add test case for EEOP_INNER_SYSVAR/EEOP_OUTER_SYSVAR executor o

2018-07-10 Thread Heikki Linnakangas
Add test case for EEOP_INNER_SYSVAR/EEOP_OUTER_SYSVAR executor opcodes. The EEOP_INNER_SYSVAR and EEOP_OUTER_SYSVAR executor opcodes are not exercised by normal queries, because setrefs.c will resolve the references to system columns in the scan nodes already. Join nodes refer to them by their pos

pgsql: Remove dynamic_shared_memory_type=none

2018-07-10 Thread Peter Eisentraut
Remove dynamic_shared_memory_type=none PostgreSQL nowadays offers some kind of dynamic shared memory feature on all supported platforms. Having the choice of "none" prevents us from relying on DSM in core features. So this patch removes the choice of "none". Author: Kyotaro Horiguchi Branch -

Re: pgsql: Fix typo

2018-07-10 Thread Alvaro Herrera
On 2018-Jul-10, Peter Eisentraut wrote: > Fix typo > > Branch > -- > REL9_5_STABLE I don't see this one in REL_10_STABLE. Was that intentional? -- Álvaro Herrerahttps://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql: Better handle pseudotypes as partition keys

2018-07-10 Thread Alvaro Herrera
Better handle pseudotypes as partition keys We fail to handle polymorphic types properly when they are used as partition keys: we were unnecessarily adding a RelabelType node on top, which confuses code examining the nodes. In particular, this makes predtest.c-based partition pruning not to work,

pgsql: Better handle pseudotypes as partition keys

2018-07-10 Thread Alvaro Herrera
Better handle pseudotypes as partition keys We fail to handle polymorphic types properly when they are used as partition keys: we were unnecessarily adding a RelabelType node on top, which confuses code examining the nodes. In particular, this makes predtest.c-based partition pruning not to work,

pgsql: Better handle pseudotypes as partition keys

2018-07-10 Thread Alvaro Herrera
Better handle pseudotypes as partition keys We fail to handle polymorphic types properly when they are used as partition keys: we were unnecessarily adding a RelabelType node on top, which confuses code examining the nodes. In particular, this makes predtest.c-based partition pruning not to work,

Re: pgsql: Fix typo

2018-07-10 Thread Peter Eisentraut
On 10.07.18 20:11, Alvaro Herrera wrote: > On 2018-Jul-10, Peter Eisentraut wrote: > >> Fix typo >> >> Branch >> -- >> REL9_5_STABLE > > I don't see this one in REL_10_STABLE. Was that intentional? I committed it to master and REL_10_STABLE a few days ago but somehow missed the other branch

Re: pgsql: Fix typo

2018-07-10 Thread Alvaro Herrera
On 2018-Jul-10, Peter Eisentraut wrote: > On 10.07.18 20:11, Alvaro Herrera wrote: > > On 2018-Jul-10, Peter Eisentraut wrote: > > > >> Fix typo > >> > >> Branch > >> -- > >> REL9_5_STABLE > > > > I don't see this one in REL_10_STABLE. Was that intentional? > > I committed it to master and

pgsql: Block replication slot advance for these not yet reserving WAL

2018-07-10 Thread Michael Paquier
Block replication slot advance for these not yet reserving WAL Such replication slots are physical slots freshly created without WAL being reserved, which is the default behavior, which have not been used yet as WAL consumption resources to retain WAL. This prevents advancing a slot to a position

pgsql: Block replication slot advance for these not yet reserving WAL

2018-07-10 Thread Michael Paquier
Block replication slot advance for these not yet reserving WAL Such replication slots are physical slots freshly created without WAL being reserved, which is the default behavior, which have not been used yet as WAL consumption resources to retain WAL. This prevents advancing a slot to a position

pgsql: Use signals for postmaster death on FreeBSD.

2018-07-10 Thread Thomas Munro
Use signals for postmaster death on FreeBSD. Use FreeBSD 11.2's new support for detecting parent process death to make PostmasterIsAlive() very cheap, as was done for Linux in an earlier commit. Author: Thomas Munro Discussion: https://postgr.es/m/7261eb39-0369-f2f4-1bb5-62f3b6083...@iki.fi Bran

pgsql: Use signals for postmaster death on Linux.

2018-07-10 Thread Thomas Munro
Use signals for postmaster death on Linux. Linux provides a way to ask for a signal when your parent process dies. Use that to make PostmasterIsAlive() very cheap. Based on a suggestion from Andres Freund. Author: Thomas Munro, Heikki Linnakangas Reviewed-By: Michael Paquier Discussion: https://

Re: Tips on committing

2018-07-10 Thread Noah Misch
On Thu, Jun 28, 2018 at 10:52:42AM -0700, Peter Geoghegan wrote: > On Thu, Jun 28, 2018 at 9:52 AM, Alvaro Herrera > wrote: > >> FWIW, I developed a document on committing for my own reference, with > >> some help from Andres. My rule has been to add to my private checklist anytime I mail or push