Re: [COMMITTERS] pgsql: Restrict file mode creation mask during tmpfile().
On Mon, Sep 21, 2015 at 01:00:46AM +, Noah Misch wrote: > Restrict file mode creation mask during tmpfile(). > REL9_0_STABLE This broke buildfarm member frogmouth (Windows, gcc) on this branch only. I will look into it. -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_1_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5f79730ec0f015e3168e822ee25554cff5fbe070 Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/246693e5ae8a36f015294aa8c73dbbf0d4e542a8 Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/8b75e489a48cc7ad61cd723180652e6fc1977911 Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/fa9fc3a1b8069c0ab5edcd6f8b0caf679fed9392 Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/3dfffac701cf95e3d9b86f12a3875f9b1b531231 Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_2_STABLE Details --- http://git.postgresql.org/pg/commitdiff/844486216eeb5b483c7b45c13b05dce76387c69a Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix possible internal overflow in numeric multiplication.
Fix possible internal overflow in numeric multiplication. mul_var() postpones propagating carries until it risks overflow in its internal digit array. However, the logic failed to account for the possibility of overflow in the carry propagation step, allowing wrong results to be generated in corner cases. We must slightly reduce the when-to-propagate-carries threshold to avoid that. Discovered and fixed by Dean Rasheed, with small adjustments by me. This has been wrong since commit d72f6c75038d8d37e64a29a04b911f728044d83b, so back-patch to all supported branches. Branch -- REL9_0_STABLE Details --- http://git.postgresql.org/pg/commitdiff/a89781e34725286b675d41f8dfdfa25ade2a277f Modified Files -- src/backend/utils/adt/numeric.c | 14 ++ src/test/regress/expected/numeric.out | 27 +++ src/test/regress/sql/numeric.sql | 12 3 files changed, 49 insertions(+), 4 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix whitespace
Fix whitespace Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/32b68ed1ba8202249e283689ccbbd8a040e67942 Modified Files -- src/interfaces/ecpg/ecpglib/execute.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix whitespace
Fix whitespace Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/a8bb248141c14911b5748bad6130e7de0cbba92e Modified Files -- src/interfaces/ecpg/ecpglib/execute.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Fix whitespace
Fix whitespace Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/13200777e7ab678d7f3535147852113ec67e6c32 Modified Files -- src/interfaces/ecpg/ecpglib/execute.c |3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: Use gender-neutral language in documentation
Use gender-neutral language in documentation Based on patch by Thomas Munro , although I rephrased most of the initial work. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/741ccd5015f82e31f80cdc5d2ae81263ea92d794 Modified Files -- doc/src/sgml/catalogs.sgml|4 +-- doc/src/sgml/client-auth.sgml |6 ++-- doc/src/sgml/ddl.sgml |6 ++-- doc/src/sgml/manage-ag.sgml |6 ++-- doc/src/sgml/nls.sgml |2 +- doc/src/sgml/plpgsql.sgml |2 +- doc/src/sgml/ref/alter_user_mapping.sgml |2 +- doc/src/sgml/ref/create_schema.sgml |2 +- doc/src/sgml/ref/create_user_mapping.sgml |2 +- doc/src/sgml/ref/drop_schema.sgml |2 +- doc/src/sgml/ref/drop_user_mapping.sgml |2 +- doc/src/sgml/ref/grant.sgml | 14 doc/src/sgml/ref/revoke.sgml |2 +- doc/src/sgml/ref/set_role.sgml|2 +- doc/src/sgml/rules.sgml | 50 ++--- doc/src/sgml/sepgsql.sgml |2 +- doc/src/sgml/sslinfo.sgml |2 +- doc/src/sgml/start.sgml |3 +- doc/src/sgml/user-manag.sgml |2 +- doc/src/sgml/xplang.sgml |2 +- 20 files changed, 57 insertions(+), 58 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: Tweak synopsis indentation for consistency
doc: Tweak synopsis indentation for consistency Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/84ae1af8f48fc910bbdacee4fc26a2145dc09657 Modified Files -- doc/src/sgml/ref/create_event_trigger.sgml |6 +++--- doc/src/sgml/ref/import_foreign_schema.sgml |8 2 files changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
[COMMITTERS] pgsql: doc: Tweak synopsis indentation for consistency
doc: Tweak synopsis indentation for consistency Branch -- REL9_5_STABLE Details --- http://git.postgresql.org/pg/commitdiff/265728e1b60858f9db8a3e7fb538477a28fc74a3 Modified Files -- doc/src/sgml/ref/create_event_trigger.sgml |6 +++--- doc/src/sgml/ref/import_foreign_schema.sgml |8 2 files changed, 7 insertions(+), 7 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Use gender-neutral language in documentation
On 2015-09-22 04:59, Peter Eisentraut wrote: Use gender-neutral language in documentation Based on patch by Thomas Munro , although I rephrased most of the initial work. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/741ccd5015f82e31f80cdc5d2ae81263ea92d794 I think this compulsive 'he'-avoiding is making the text worse. - environment variable); any user can make such a change for his session. + environment variable); any user can make such a change for their session. Yuck. even worse: - might not be the same as the database user he needs to connect as. + might not be the same as the database user that is to be connect as. It is not an improvement. I would like to see this change rolled back. thanks, Erik Rijkers -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
Re: [COMMITTERS] pgsql: Use gender-neutral language in documentation
On Mon, Sep 21, 2015 at 9:32 PM, Erik Rijkers wrote: > I think this compulsive 'he'-avoiding is making the text worse. > > > - environment variable); any user can make such a change for his > session. > + environment variable); any user can make such a change for their > session. -1. It seems fine to me. > Yuck. even worse: > > - might not be the same as the database user he needs to connect as. > + might not be the same as the database user that is to be connect as. > > > It is not an improvement. I would like to see this change rolled back. I think that this should be reworded, since there is a grammatical error as things stand. I suggest the whole sentence be modified to read: When using an external authentication system such as Ident or GSSAPI, the name of the operating system user that initiated the connection might not be the same as the intended corresponding database user. -- Peter Geoghegan -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
