pgsql: Remove another unnecessary application_name specification in tes

2019-03-16 Thread Peter Eisentraut
Remove another unnecessary application_name specification in test see 8e93a516e68bac3c329fd2e7f423ee9aceca943a Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/0176eb210e445e8a911c7df79997c7ab62e86dcc Modified Files -- src/test/subscription/t/100_bugs.pl

pgsql: Further adjust the tests for the hyperbolic functions.

2019-03-16 Thread Tom Lane
Further adjust the tests for the hyperbolic functions. It looks like we can leave in most of the test cases for Infinity/NaN inputs, but buildfarm member jacana gets the wrong answer for acosh(Inf). It's not worth carrying a variant expected file for that, so just disable that one test. Discussio

Re: pgsql: Partial implementation of SQL/JSON path language

2019-03-16 Thread Alexander Korotkov
сб, 16 мар. 2019 г., 18:50 Tom Lane : > Alexander Korotkov writes: > > Partial implementation of SQL/JSON path language > > Please fix the compiler warnings this produces. > > jsonpath_exec.c: In function 'executePredicate': > jsonpath_exec.c:1458: warning: 'rseqit.next' may be used uninitialized

pgsql: Suppress -Wimplicit-fallthrough warnings in new jsonpath code.

2019-03-16 Thread Tom Lane
Suppress -Wimplicit-fallthrough warnings in new jsonpath code. Per buildfarm. See commit 41c912cad for precedent. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/20f7c3d5606254d8870697f15fd7a7b4e602e1e1 Modified Files -- src/backend/utils/adt/jsonpath.

Re: pgsql: Partial implementation of SQL/JSON path language

2019-03-16 Thread Tom Lane
Alexander Korotkov writes: > Partial implementation of SQL/JSON path language Please fix the compiler warnings this produces. jsonpath_exec.c: In function 'executePredicate': jsonpath_exec.c:1458: warning: 'rseqit.next' may be used uninitialized in this function jsonpath_exec.c:1458: warning: '

pgsql: Update copyright year in files added by 1bb5e78218.

2019-03-16 Thread Amit Kapila
Update copyright year in files added by 1bb5e78218. Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/f27314ff9a0eb60b75bb576c3629c8849f7698c1 Modified Files -- src/backend/partitioning/partdesc.c | 2 +- src/include/partitioning/partdesc.h | 2 +- 2 files c

pgsql: Numeric error suppression in jsonpath

2019-03-16 Thread Alexander Korotkov
Numeric error suppression in jsonpath Add support of numeric error suppression to jsonpath as it's required by standard. This commit doesn't use PG_TRY()/PG_CATCH() in order to implement that. Instead, it provides internal versions of numeric functions used, which support error suppression. Dis

pgsql: Partial implementation of SQL/JSON path language

2019-03-16 Thread Alexander Korotkov
Partial implementation of SQL/JSON path language SQL 2016 standards among other things contains set of SQL/JSON features for JSON processing inside of relational database. The core of SQL/JSON is JSON path language, allowing access parts of JSON documents and make computations over them. This co

pgsql: Avoid casting away a const

2019-03-16 Thread Peter Eisentraut
Avoid casting away a const Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/893d6f8a1f9b43da805124e93cbf0f7aea890ad4 Modified Files -- src/backend/access/transam/xlog.c | 2 +- src/backend/utils/misc/guc.c | 2 +- src/include/access/xlog.h | 2

pgsql: Don't propagate PGAPPNAME through pg_ctl in tests

2019-03-16 Thread Peter Eisentraut
Don't propagate PGAPPNAME through pg_ctl in tests When libpq is loaded in the server (for instance, by libpqwalreceiver), it may use libpq environment variables set in the postmaster environment for connection parameter defaults. This has some confusing effects in our test suites. For example, t