[COMMITTERS] pgsql: fix a perl typo

fix a perl typo Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9892cc20097e8934b76965d97a86775d6d5d49bf Modified Files -- src/tools/msvc/vcregress.pl |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing l

[COMMITTERS] pgsql: fix a perl typo

fix a perl typo Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3f222b676d5c2fe2a7d869c80b8f840e2ae47b41 Modified Files -- src/tools/msvc/vcregress.pl |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing l

[COMMITTERS] pgsql: fix a perl typo

fix a perl typo Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/f11c557e92c50d3d613d1173c15feb5310ba4744 Modified Files -- src/tools/msvc/vcregress.pl |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-committers mailing list (pg

[COMMITTERS] pgsql: Improve vcregress.pl's handling of tap tests for client programs

Improve vcregress.pl's handling of tap tests for client programs The target is now named 'bincheck' rather than 'tapcheck' so that it reflects what is checked instead of the test mechanism. Some of the logic is improved, making it easier to add further sets of TAP based tests in future. Also, the

[COMMITTERS] pgsql: Update docs for vcregress.pl bincheck changes

Update docs for vcregress.pl bincheck changes Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/bfac7a69ba5d2dd9b77b9de5daa7de9920426377 Modified Files -- doc/src/sgml/install-windows.sgml |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

[COMMITTERS] pgsql: Improve vcregress.pl's handling of tap tests for client programs

Improve vcregress.pl's handling of tap tests for client programs The target is now named 'bincheck' rather than 'tapcheck' so that it reflects what is checked instead of the test mechanism. Some of the logic is improved, making it easier to add further sets of TAP based tests in future. Also, the

[COMMITTERS] pgsql: Update docs for vcregress.pl bincheck changes

Update docs for vcregress.pl bincheck changes Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/0fbf440407ae4ae34c143579ab2fc68f37895856 Modified Files -- doc/src/sgml/install-windows.sgml |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

[COMMITTERS] pgsql: Update docs for vcregress.pl bincheck changes

Update docs for vcregress.pl bincheck changes Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c2d5657c0f6f8ae9894205551354eca796f8b11c Modified Files -- doc/src/sgml/install-windows.sgml |6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --

[COMMITTERS] pgsql: Improve vcregress.pl's handling of tap tests for client programs

Improve vcregress.pl's handling of tap tests for client programs The target is now named 'bincheck' rather than 'tapcheck' so that it reflects what is checked instead of the test mechanism. Some of the logic is improved, making it easier to add further sets of TAP based tests in future. Also, the

[COMMITTERS] pgsql: Fix incomplete set_foreignscan_references handling for fdw_reche

Fix incomplete set_foreignscan_references handling for fdw_recheck_quals KaiGai Kohei Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5021e3dac9878134ded01806807a9e17f9324425 Modified Files -- src/backend/optimizer/plan/setrefs.c |6 ++ 1 f

[COMMITTERS] pgsql: Fix incomplete set_foreignscan_references handling for fdw_reche

Fix incomplete set_foreignscan_references handling for fdw_recheck_quals KaiGai Kohei Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/7907a949abf100b5a1e1def1184ba1e6fc8b9fd7 Modified Files -- src/backend/optimizer/plan/setrefs.c |6 ++ 1 file cha

[COMMITTERS] pgsql: Improve ON CONFLICT documentation.

Improve ON CONFLICT documentation. Author: Peter Geoghegan and Andres Freund Discussion: cam3swzscpwzq-7ejc77vwqzz1go8gnmurq1qqdq3wrn7abw...@mail.gmail.com Backpatch: 9.5, where ON CONFLICT was introduced Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/af85779

[COMMITTERS] pgsql: Improve ON CONFLICT documentation.

Improve ON CONFLICT documentation. Author: Peter Geoghegan and Andres Freund Discussion: cam3swzscpwzq-7ejc77vwqzz1go8gnmurq1qqdq3wrn7abw...@mail.gmail.com Backpatch: 9.5, where ON CONFLICT was introduced Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/edf68b2ed51cb8

[COMMITTERS] pgsql: Remove function names from some elog() calls in heapam.c.

Remove function names from some elog() calls in heapam.c. At least one of the names was, due to a function renaming late in the development of ON CONFLICT, wrong. Since including function names in error messages is against the message style guide anyway, remove them from the messages. Discussion:

[COMMITTERS] pgsql: Remove function names from some elog() calls in heapam.c.

Remove function names from some elog() calls in heapam.c. At least one of the names was, due to a function renaming late in the development of ON CONFLICT, wrong. Since including function names in error messages is against the message style guide anyway, remove them from the messages. Discussion:

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- master Details --- http://git.postgresql.org/p

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- REL9_5_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- REL9_4_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- REL9_2_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- REL9_1_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Accept flex > 2.5.x in configure.

Accept flex > 2.5.x in configure. Per buildfarm member anchovy, 2.6.0 exists in the wild now. Hopefully it works with Postgres; if not, we'll have to do something about that, but in any case claiming it's "too old" is pretty silly. Branch -- REL9_3_STABLE Details --- http://git.postgresq

[COMMITTERS] pgsql: Make a comment more precise.

Make a comment more precise. Remote expressions now also matter to make_foreignscan() Noted by Etsuro Fujita. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/e073490457176805bc31b8f7c7829ce1b71a6e76 Modified Files -- contrib/postgres_fdw/postgres_fdw.c

[COMMITTERS] pgsql: Avoid aggregating worker instrumentation multiple times.

Avoid aggregating worker instrumentation multiple times. Amit Kapila, per design ideas from me. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/166b61a88ef8e9fb97eba7b7ab8062e214c93af8 Modified Files -- src/backend/executor/execParallel.c | 18

[COMMITTERS] pgsql: Fix dumb bug in tqueue.c

Fix dumb bug in tqueue.c When I wrote this code originally, the intention was to recompute the remapinfo only when the tupledesc changes. This presumably only happens once per query, but I copied the design pattern from other DestReceivers. However, due to a silly oversight on my part, tqueue->t

Re: [COMMITTERS] pgsql: Generate parallel sequential scan plans in simple cases.

On Wed, Nov 11, 2015 at 11:06 PM, Peter Geoghegan wrote: > > On Wed, Nov 11, 2015 at 9:08 AM, Peter Geoghegan wrote: > > Congratulations, Robert. > > I should certainly extend my congratulations to Amit too. > Thanks! With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com