[COMMITTERS] pgsql: Fix typo in C comment.

Fix typo in C comment. Merlin Moncure Backpatch to 9.5, where the misspelling was introduced Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/57823244ad087a2dc807a6e60fefce26f81bd5dc Modified Files -- src/backend/commands/trigger.c |2 +- 1 file

[COMMITTERS] pgsql: Fix typo in C comment.

Fix typo in C comment. Merlin Moncure Backpatch to 9.5, where the misspelling was introduced Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/5956b7f9e858ac5613dd0214ac7fb2476f900771 Modified Files -- src/backend/commands/trigger.c |2 +- 1 file change

[COMMITTERS] pgsql: Avoid use of float arithmetic in bipartite_match.c.

Avoid use of float arithmetic in bipartite_match.c. Since the distances used in this algorithm are small integers (not more than the size of the U set, in fact), there is no good reason to use float arithmetic for them. Use short ints instead: they're smaller, faster, and require no special porta

[COMMITTERS] pgsql: Avoid use of float arithmetic in bipartite_match.c.

Avoid use of float arithmetic in bipartite_match.c. Since the distances used in this algorithm are small integers (not more than the size of the U set, in fact), there is no good reason to use float arithmetic for them. Use short ints instead: they're smaller, faster, and require no special porta

Re: [COMMITTERS] pgsql: Avoid use of float arithmetic in bipartite_match.c.

Hi, On 2015-08-23 17:02:35 +, Tom Lane wrote: > Avoid use of float arithmetic in bipartite_match.c. > > Since the distances used in this algorithm are small integers (not more > than the size of the U set, in fact), there is no good reason to use float > arithmetic for them. Use short ints i

Re: [COMMITTERS] pgsql: Avoid use of float arithmetic in bipartite_match.c.

Andres Freund writes: > Not sure why you replaced n by k? I thought it was possible to confuse it with the "n"'s used in the previous line to denote the graph sizes. > the nodes are 1..n, so the adjacency list should be as well (or the > other way round). No, I meant them to be different. Do y

Re: [COMMITTERS] pgsql: Avoid use of float arithmetic in bipartite_match.c.

On 2015-08-23 13:30:45 -0400, Tom Lane wrote: > Andres Freund writes: > > Not sure why you replaced n by k? > > I thought it was possible to confuse it with the "n"'s used in the > previous line to denote the graph sizes. > > > the nodes are 1..n, so the adjacency list should be as well (or the

[COMMITTERS] pgsql: Reduce number of bytes examined by convert_one_string_to_scalar(

Reduce number of bytes examined by convert_one_string_to_scalar(). Previously, convert_one_string_to_scalar() would examine up to 20 bytes of the input string, producing a scalar conversion with theoretical precision far greater than is of any possible use considering the other limitations on the

[COMMITTERS] pgsql: Tweak wording of syntax error messages about bad CONTINUE/EXIT s

Tweak wording of syntax error messages about bad CONTINUE/EXIT statements. Try to avoid any possible confusion about what these messages mean. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/18391a8f0649f40bb841e6492895551fd873f79b Modified Files -- src/