[COMMITTERS] pgsql: Change wording for COALESCE docs to use "otherwise".

Change wording for COALESCE docs to use "otherwise". Per Tom Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/3919ad864d7040361fd4b44719acaa1ec0f87bbd Modified Files -- doc/src/sgml/func.sgml |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)

[COMMITTERS] pgsql: Explain COALESCE example in the docs.

Explain COALESCE example in the docs. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/9d23d7cdafb3540aa2de9310c7f1afee87dfc2f2 Modified Files -- doc/src/sgml/func.sgml |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) -- Sent via pgsql-committ

[COMMITTERS] pgsql: Improve define_custom_variable's handling of pre-existing settin

Improve define_custom_variable's handling of pre-existing settings. Arrange for any problems with pre-existing settings to be reported as WARNING not ERROR, so that we don't undesirably abort the loading of the incoming add-on module. The bad setting is just discarded, as though it had never been

[COMMITTERS] pgsql: Fix uninitialized-variable bug.

Fix uninitialized-variable bug. Branch -- master Details --- http://git.postgresql.org/pg/commitdiff/fa56a0c3e01c175695e932e6cdc2c6915df5adc6 Modified Files -- src/backend/access/transam/slru.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-

[COMMITTERS] pgsql: Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission

Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission files. This oversight meant that on Windows, the pg_settings view would not display source file or line number information for values coming from postgresql.conf, unless the backend had received a SIGHUP since starting. In passing, a

[COMMITTERS] pgsql: Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission

Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission files. This oversight meant that on Windows, the pg_settings view would not display source file or line number information for values coming from postgresql.conf, unless the backend had received a SIGHUP since starting. In passing, a

[COMMITTERS] pgsql: Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission

Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission files. This oversight meant that on Windows, the pg_settings view would not display source file or line number information for values coming from postgresql.conf, unless the backend had received a SIGHUP since starting. In passing, a

[COMMITTERS] pgsql: Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission

Add sourcefile/sourceline data to EXEC_BACKEND GUC transmission files. This oversight meant that on Windows, the pg_settings view would not display source file or line number information for values coming from postgresql.conf, unless the backend had received a SIGHUP since starting. In passing, a

[COMMITTERS] pgsql: Remember the source GucContext for each GUC parameter.

Remember the source GucContext for each GUC parameter. We used to just remember the GucSource, but saving GucContext too provides a little more information --- notably, whether a SET was done by a superuser or regular user. This allows us to rip out the fairly dodgy code that define_custom_variab

[COMMITTERS] pgsql: Use callbacks in SlruScanDirectory for the actual action

Use callbacks in SlruScanDirectory for the actual action Previously, the code assumed that the only possible action to take was to delete files behind a certain cutoff point. The async notify code was already a crock: it used a different "pagePrecedes" function for truncation than for regular ope

[COMMITTERS] pgsql: Remove the custom_variable_classes parameter.

Remove the custom_variable_classes parameter. This variable provides only marginal error-prevention capability (since it can only check the prefix of a qualified GUC name), and the consensus is that that isn't worth the amount of hassle that maintaining the setting creates for DBAs. So, let's jus