[COMMITTERS] pgsql: Fix missing space in documentation

Fix missing space in documentation Ian Barwick Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/6d6cade05bcb68ca8677aa5502ca73274d6e4539 Modified Files -- doc/src/sgml/wal.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via pgsql-c

[COMMITTERS] pgsql: Fix missing space in documentation

Fix missing space in documentation Ian Barwick Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5c9a4a866efcc15ec041134538e01f25c2e2bd88 Modified Files -- doc/src/sgml/wal.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via

[COMMITTERS] pgsql: Fix missing space in documentation

Fix missing space in documentation Ian Barwick Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/76394810f87d3c03f8a135cc6e9801acc6b0ad8d Modified Files -- doc/src/sgml/wal.sgml |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via

[COMMITTERS] pgsql: Put SSL_pending() call behind the new internal SSL API.

Put SSL_pending() call behind the new internal SSL API. It seems likely that any SSL implementation will need a similar call, not just OpenSSL. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/4e86f1b16da85ba0a99c592dc7b977b3be80a483 Modified Files -- src

[COMMITTERS] pgsql: Fix hstore_to_json_loose's detection of valid JSON number values

Fix hstore_to_json_loose's detection of valid JSON number values. We expose a function IsValidJsonNumber that internally calls the lexer for json numbers. That allows us to use the same test everywhere, instead of inventing a broken test for hstore conversions. The new function is also used in dat

[COMMITTERS] pgsql: Fix hstore_to_json_loose's detection of valid JSON number values

Fix hstore_to_json_loose's detection of valid JSON number values. We expose a function IsValidJsonNumber that internally calls the lexer for json numbers. That allows us to use the same test everywhere, instead of inventing a broken test for hstore conversions. The new function is also used in dat

[COMMITTERS] pgsql: Fix hstore_to_json_loose's detection of valid JSON number values

Fix hstore_to_json_loose's detection of valid JSON number values. We expose a function IsValidJsonNumber that internally calls the lexer for json numbers. That allows us to use the same test everywhere, instead of inventing a broken test for hstore conversions. The new function is also used in dat

[COMMITTERS] pgsql: Fix backpatching error in commit 55c88079

Fix backpatching error in commit 55c88079 Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9e05f3b97e63c34411669aee139c4a6236c68030 Modified Files -- src/backend/utils/adt/json.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- Sent via

[COMMITTERS] pgsql: Move security_label test

Move security_label test Rather than have the core security_label regression test depend on the dummy_seclabel module, have that part of the test be executed by dummy_seclabel itself directly. This simplifies the testing rig a bit; in particular it should silence the problems from the MSVC buildf

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

[COMMITTERS] pgsql: Guard against bad "dscale" values in numeric_recv().

Guard against bad "dscale" values in numeric_recv(). We were not checking to see if the supplied dscale was valid for the given digit array when receiving binary-format numeric values. While dscale can validly be more than the number of nonzero fractional digits, it shouldn't be less; that case c

Re: [COMMITTERS] pgsql: Move security_label test

On Tue, Dec 2, 2014 at 4:13 AM, Alvaro Herrera wrote: > Move security_label test > > Rather than have the core security_label regression test depend on the > dummy_seclabel module, have that part of the test be executed by > dummy_seclabel itself directly. This simplifies the testing rig a bit; >