[COMMITTERS] pgsql: Make a editorial pass over pgbench's error messages.

2015-07-05 Thread Tom Lane
Make a editorial pass over pgbench's error messages. The lack of consistency, and lack of attention to our message style guidelines, was a bit striking. Try to make 'em better. Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/c7673d2b1fd54caa82c9870927d0bef651

[COMMITTERS] pgsql: Make a editorial pass over pgbench's error messages.

2015-07-05 Thread Tom Lane
Make a editorial pass over pgbench's error messages. The lack of consistency, and lack of attention to our message style guidelines, was a bit striking. Try to make 'em better. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/22ba5563adacd162d97ff3c80eac4893574f1e17

[COMMITTERS] pgsql: Fix some typos in regression test comments.

2015-07-05 Thread Tom Lane
Fix some typos in regression test comments. Back-patch to avoid unnecessary cross-branch differences. CharSyam Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/353f4fde794fca07f6f654219a12d8087930fa28 Modified Files -- src/test/regress/expected/al

[COMMITTERS] pgsql: Fix some typos in regression test comments.

2015-07-05 Thread Tom Lane
Fix some typos in regression test comments. Back-patch to avoid unnecessary cross-branch differences. CharSyam Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/486d3a2bb4b9e4c1cc64241f4b36643a22da8693 Modified Files -- src/test/regress/expected/al

[COMMITTERS] pgsql: Fix some typos in regression test comments.

2015-07-05 Thread Tom Lane
Fix some typos in regression test comments. Back-patch to avoid unnecessary cross-branch differences. CharSyam Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/551654977022097ac408b483b3be9887a99f0ce0 Modified Files -- src/test/regress/expected/alter_gen

[COMMITTERS] pgsql: Further reduce overhead for passing plpgsql variables to the exe

2015-07-05 Thread Tom Lane
Further reduce overhead for passing plpgsql variables to the executor. This builds on commit 21dcda2713656a7483e3280ac9d2ada20a87a9a9 by keeping a plpgsql function's shared ParamListInfo's entries for simple variables (PLPGSQL_DTYPE_VARs) valid at all times. That adds a few cycles to each assignm

[COMMITTERS] pgsql: Fix bad grammar in brin.sgml.

2015-07-05 Thread Tom Lane
Fix bad grammar in brin.sgml. Christoph Berg Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/252404625aa98fa5f93a45a8dcffdc179981820a Modified Files -- doc/src/sgml/brin.sgml |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsq

[COMMITTERS] pgsql: Fix bad grammar in brin.sgml.

2015-07-05 Thread Tom Lane
Fix bad grammar in brin.sgml. Christoph Berg Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9a92ad4b9eec0051296d6475feb9c9955c860a9d Modified Files -- doc/src/sgml/brin.sgml |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- Sent v

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

[COMMITTERS] pgsql: Make numeric form of PG version number readily available in Make

2015-07-05 Thread Tom Lane
Make numeric form of PG version number readily available in Makefiles. Expose PG_VERSION_NUM (e.g., "90600") as a Make variable; but for consistency with the other Make variables holding similar info, call the variable just VERSION_NUM not PG_VERSION_NUM. There was some discussion of making this

Re: [COMMITTERS] pgsql: Add missing_ok option to the SQL functions for reading files.

2015-07-05 Thread Michael Paquier
On Mon, Jun 29, 2015 at 3:39 AM, Heikki Linnakangas wrote: > Add missing_ok option to the SQL functions for reading files. > > This makes it possible to use the functions without getting errors, if there > is a chance that the file might be removed or renamed concurrently. > pg_rewind needs to do