[COMMITTERS] pgsql: Fix function declaration style to respect the coding standard.
Fix function declaration style to respect the coding standard. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/527e6d3f099df22783465ca7046fc0c8a534c921 Modified Files -- src/bin/pgbench/pgbench.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 function declaration style to respect the coding standard.
Fix function declaration style to respect the coding standard. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/fc7f6e331d7d35f7f24f72a62e4907887e7bcb11 Modified Files -- contrib/pgbench/pgbench.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 function declaration style to respect the coding standard.
Fix function declaration style to respect the coding standard. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/9a437994400f5fdadac103fc5df0c5d622d5c8be Modified Files -- contrib/pgbench/pgbench.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 comment for GetCurrentIntegerTimestamp().
Fix comment for GetCurrentIntegerTimestamp(). The unit of measure is microseconds, not milliseconds. Backpatch to 9.3 where the function and its comment were added. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/f9b38ab6536e0c175cf94bea0c8f2a3d9fed175a Modified Files -- src/backend/utils/adt/timestamp.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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 comment for GetCurrentIntegerTimestamp().
Fix comment for GetCurrentIntegerTimestamp(). The unit of measure is microseconds, not milliseconds. Backpatch to 9.3 where the function and its comment were added. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/cca8ba9529f8815acd23fe88c32763765d0e1b68 Modified Files -- src/backend/utils/adt/timestamp.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- 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: Fix the fallback memory barrier implementation to be reentrant.
Andres Freund and...@anarazel.de writes: Fix the fallback memory barrier implementation to be reentrant. Seems this has not done the trick: anole just crashed with stuck spinlock again. regards, tom lane -- 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: Run the C portions of guc-file.l through pgindent.
Run the C portions of guc-file.l through pgindent. Yeah, I know, pretty anal-retentive of me. But we oughta find some way to automate this for the .y and .l files. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/2bdc51a2946f9a66688eb705cd0cb584ebd8240a Modified Files -- src/backend/utils/misc/guc-file.l | 106 +++-- 1 file changed, 54 insertions(+), 52 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: Improve design and implementation of pg_file_settings view.
Improve design and implementation of pg_file_settings view. As first committed, this view reported on the file contents as they were at the last SIGHUP event. That's not as useful as reporting on the current contents, and what's more, it didn't work right on Windows unless the current session had serviced at least one SIGHUP. Therefore, arrange to re-read the files when pg_show_all_settings() is called. This requires only minor refactoring so that we can pass changeVal = false to set_config_option() so that it won't actually apply any changes locally. In addition, add error reporting so that errors that would prevent the configuration files from being loaded, or would prevent individual settings from being applied, are visible directly in the view. This makes the view usable for pre-testing whether edits made in the config files will have the desired effect, before one actually issues a SIGHUP. I also added an applied column so that it's easy to identify entries that are superseded by later entries; this was the main use-case for the original design, but it seemed unnecessarily hard to use for that. Also fix a 9.4.1 regression that allowed multiple entries for a PGC_POSTMASTER variable to cause bogus complaints in the postmaster log. (The issue here was that commit bf007a27acd7b2fb unintentionally reverted 3e3f65973a3c94a6, which suppressed any duplicate entries within ParseConfigFp. However, since the original coding of the pg_file_settings view depended on such suppression *not* happening, we couldn't have fixed this issue now without first doing something with pg_file_settings. Now we suppress duplicates by marking them ignored within ProcessConfigFileInternal, which doesn't hide them in the view.) Lesser changes include: Drive the view directly off the ConfigVariable list, instead of making a basically-equivalent second copy of the data. There's no longer any need to hang onto the data permanently, anyway. Convert show_all_file_settings() to do its work in one call and return a tuplestore; this avoids risks associated with assuming that the GUC state will hold still over the course of query execution. (I think there were probably latent bugs here, though you might need something like a cursor on the view to expose them.) Arrange to run SIGHUP processing in a short-lived memory context, to forestall process-lifespan memory leaks. (There is one known leak in this code, in ProcessConfigDirectory; it seems minor enough to not be worth back-patching a specific fix for.) Remove mistaken assignment to ConfigFileLineno that caused line counting after an include_dir directive to be completely wrong. Add missed failure check in AlterSystemSetConfigFile(). We don't really expect ParseConfigFp() to fail, but that's not an excuse for not checking. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/62d16c7fc5614d9f4d0dd1a9f164b232c273c128 Modified Files -- doc/src/sgml/catalogs.sgml | 72 +-- doc/src/sgml/config.sgml|8 + doc/src/sgml/release-9.5.sgml | 15 +- src/backend/utils/misc/guc-file.l | 369 +++ src/backend/utils/misc/guc.c| 181 + src/include/catalog/catversion.h|2 +- src/include/catalog/pg_proc.h |2 +- src/include/utils/guc.h | 20 +- src/test/regress/expected/rules.out |6 +- 9 files changed, 430 insertions(+), 245 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: Back-patch some minor bug fixes in GUC code.
Back-patch some minor bug fixes in GUC code. In 9.4, fix a 9.4.1 regression that allowed multiple entries for a PGC_POSTMASTER variable to cause bogus complaints in the postmaster log. (The issue here was that commit bf007a27acd7b2fb unintentionally reverted 3e3f65973a3c94a6, which suppressed any duplicate entries within ParseConfigFp. Back-patch the reimplementation just made in HEAD, which makes use of an ignore field to prevent application of superseded items.) Add missed failure check in AlterSystemSetConfigFile(). We don't really expect ParseConfigFp() to fail, but that's not an excuse for not checking. In both 9.3 and 9.4, remove mistaken assignment to ConfigFileLineno that caused line counting after an include_dir directive to be completely wrong. Branch -- REL9_3_STABLE Details --- http://git.postgresql.org/pg/commitdiff/5a56c254588a91de393b8ce99f8deeefc6a44d67 Modified Files -- src/backend/utils/misc/guc-file.l |1 - 1 file changed, 1 deletion(-) -- 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: Back-patch some minor bug fixes in GUC code.
Back-patch some minor bug fixes in GUC code. In 9.4, fix a 9.4.1 regression that allowed multiple entries for a PGC_POSTMASTER variable to cause bogus complaints in the postmaster log. (The issue here was that commit bf007a27acd7b2fb unintentionally reverted 3e3f65973a3c94a6, which suppressed any duplicate entries within ParseConfigFp. Back-patch the reimplementation just made in HEAD, which makes use of an ignore field to prevent application of superseded items.) Add missed failure check in AlterSystemSetConfigFile(). We don't really expect ParseConfigFp() to fail, but that's not an excuse for not checking. In both 9.3 and 9.4, remove mistaken assignment to ConfigFileLineno that caused line counting after an include_dir directive to be completely wrong. Branch -- REL9_4_STABLE Details --- http://git.postgresql.org/pg/commitdiff/1afc1fe9c7bb72652ff9681c2e59a5751a33cda1 Modified Files -- src/backend/utils/misc/guc-file.l | 50 ++--- src/backend/utils/misc/guc.c |6 - src/include/utils/guc.h |6 - 3 files changed, 51 insertions(+), 11 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: Run the C portions of guc-file.l through pgindent.
On Mon, Jun 29, 2015 at 9:49 AM, Tom Lane t...@sss.pgh.pa.us wrote: Run the C portions of guc-file.l through pgindent. Yeah, I know, pretty anal-retentive of me. But we oughta find some way to automate this for the .y and .l files. .y files may be tricky and .l files less. Still one good way to test such things would be to use something like that and see at least what happens when doing a run (haven't tested, use at your own risk): diff --git a/src/tools/pgindent/pgindent b/src/tools/pgindent/pgindent index 0d3859d..3995214 100755 --- a/src/tools/pgindent/pgindent +++ b/src/tools/pgindent/pgindent @@ -519,6 +519,7 @@ File::Find::find( (($dev, $ino, $mode, $nlink, $uid, $gid) = lstat($_)) -f _ /^.*\.[ch]\z/s + /^.*\.(h|c|y|l)\z/s push(@files, $File::Find::name); } }, Regards, -- Michael -- 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: Translation updates
Translation updates Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git Source-Git-Hash: fb7e72f46cfafa1b5bfe4564d9686d63a1e6383f Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/c5e5d444de85a7caff462443c5915544d4406a62 Modified Files -- src/backend/po/de.po |10095 +++--- src/backend/po/fr.po | 9467 +++ src/backend/po/ru.po | 2699 - src/bin/initdb/po/de.po | 370 +- src/bin/initdb/po/fr.po | 335 +- src/bin/pg_basebackup/po/de.po | 480 +- src/bin/pg_basebackup/po/fr.po | 772 +-- src/bin/pg_config/po/fr.po |2 +- src/bin/pg_controldata/po/de.po | 191 +- src/bin/pg_controldata/po/fr.po |2 +- src/bin/pg_ctl/po/fr.po |2 +- src/bin/pg_dump/po/de.po | 1000 ++-- src/bin/pg_dump/po/fr.po |2 +- src/bin/pg_resetxlog/po/de.po| 305 +- src/bin/pg_resetxlog/po/fr.po|2 +- src/bin/pg_rewind/nls.mk |2 +- src/bin/pg_rewind/po/de.po | 785 +++ src/bin/psql/po/de.po| 3156 +++ src/bin/psql/po/fr.po| 3921 ++--- src/bin/scripts/po/de.po | 248 +- src/bin/scripts/po/fr.po | 231 +- src/interfaces/ecpg/ecpglib/po/fr.po |2 +- src/interfaces/ecpg/preproc/po/fr.po |2 +- src/interfaces/libpq/po/de.po| 239 +- src/interfaces/libpq/po/fr.po| 500 +- src/pl/plperl/po/fr.po |2 +- src/pl/plpgsql/src/po/fr.po |2 +- src/pl/plpython/po/fr.po | 138 +- src/pl/tcl/po/fr.po |2 +- 29 files changed, 17378 insertions(+), 17576 deletions(-) -- Sent via pgsql-committers mailing list (pgsql-committers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
