pgsql: Try to stabilize EXPLAIN output in partition_check test.

Try to stabilize EXPLAIN output in partition_check test. Commit 7d8ac9814bc9bb6df2d845dbabed38d7284c7c2c adjusted these tests in the hope of preserving the plan shape, but I failed to notice that the three partitions were, on my local machine, choosing two different plan shapes. This is probably

pgsql: Add user-callable SHA-2 functions

Add user-callable SHA-2 functions Add the user-callable functions sha224, sha256, sha384, sha512. We already had these in the C code to support SCRAM, but there was no test coverage outside of the SCRAM tests. Adding these as user-callable functions allows writing some tests. Also, we have a

pgsql: Be lazier about partition tuple routing.

Be lazier about partition tuple routing. It's not necessary to fully initialize the executor data structures for partitions to which no tuples are ever routed. Consider, for example, an INSERT statement that inserts only one row: it only cares about the partition to which that one row is routed.

pgsql: Fix perlcritic warnings

Fix perlcritic warnings Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/abcba7001e481a565b8fba2393666dc54e90db61 Modified Files -- src/bin/pgbench/t/001_pgbench_with_server.pl | 8 1 file changed, 4 insertions(+), 4 deletions(-)

pgsql: Remove extra words.

Remove extra words. Thomas Munro Discussion: http://postgr.es/m/CAEepm=2x3NUSPed6=-wdys39ktuu5dw3mk_namwps+18fmk...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/a6a80134e3bffa0678a82ed7477d9d46dea07d3a Modified Files --

pgsql: Support parameters in CALL

Support parameters in CALL To support parameters in CALL, move the parse analysis of the procedure and arguments into the global transformation phase, so that the parser hooks can be applied. And then at execution time pass the parameters from ProcessUtility on to ExecuteCallStmt. Branch --

pgsql: postgres_fdw: Fix interaction of PHVs with child joins.

postgres_fdw: Fix interaction of PHVs with child joins. Commit f49842d1ee31b976c681322f76025d7732e860f3 introduced the concept of a child join, but did not update this code accordingly. Ashutosh Bapat, with cosmetic changes by me Discussion:

pgsql: Remove extra word from comment.

Remove extra word from comment. Etsuro Fujita Discussion: http://postgr.es/m/5a8eaf74.5010...@lab.ntt.co.jp Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/810e7e264ab547c404e32dba4f8733db53912084 Modified Files -- src/backend/executor/execPartition.c

Re: pgsql: Avoid valgrind complaint about write() of uninitalized bytes.

On Wed, Feb 21, 2018 at 3:18 PM, Peter Geoghegan wrote: > On Wed, Feb 21, 2018 at 10:55 AM, Peter Geoghegan wrote: >> Sure, but it looks like it has the exact same underlying cause to the >> LogicalTapeFreeze() issue. It shouldn't be very hard to write an >>