From ea23ec82c2ec2ac14007f002692743b67b18f80f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 14 Nov 2004 19:35:35 +0000 Subject: Remove GUC USERLIMIT variable category, making the affected variables plain SUSET instead. Also delay processing of options received in client connection request until after we know if the user is a superuser, so that SUSET values can be set that way by legitimate superusers. Per recent discussion. --- doc/src/sgml/runtime.sgml | 47 ++++++++++++++++++++++------------------------- 1 file changed, 22 insertions(+), 25 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/runtime.sgml b/doc/src/sgml/runtime.sgml index 91cdec32284..8dbd65454b2 100644 --- a/doc/src/sgml/runtime.sgml +++ b/doc/src/sgml/runtime.sgml @@ -1,5 +1,5 @@ @@ -2150,7 +2150,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 to the log. The default is NOTICE. Note that LOG has a different rank here than in client_min_messages. - Only superusers can increase this option. + Only superusers can change this setting. @@ -2186,7 +2186,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 SQL statements causing errors, fatal errors, or panics will be logged. Enabling this option can be helpful in tracking down the source of any errors that appear in the server log. - Only superusers can increase this option. + Only superusers can change this setting. @@ -2204,8 +2204,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 250 then all SQL statements that run 250ms or longer will be logged. Enabling this option can be useful in tracking down unoptimized queries in your applications. - Only superusers can increase this or set it to minus-one if this - option is set by the administrator. + Only superusers can change this setting. @@ -2332,7 +2331,7 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 these displays to produce a more readable but much longer output format. client_min_messages or log_min_messages must be - DEBUG1 or lower to send output to the + DEBUG1 or lower to send the output to the client or server logs. These options are off by default. @@ -2372,10 +2371,9 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 log_statement to be logged. When using this option, if you are not using syslog, it is recommended that you log the PID or session ID using log_line_prefix - or log the session ID so that you can link the statement to the + so that you can link the statement to the duration using the process ID or session ID. The default is off. - Only superusers can turn off this option if it is enabled by the - administrator. + Only superusers can change this setting. @@ -2487,35 +2485,35 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 Controls which SQL statements are logged. Valid values are - all, ddl, mod, and - none. ddl logs all data definition + none, ddl, mod, and + all. ddl logs all data definition commands like CREATE, ALTER, and DROP commands. mod logs all ddl statements, plus INSERT, UPDATE, DELETE, TRUNCATE, and COPY FROM. PREPARE and - EXPLAIN ANALYZE statements are also considered for - appropriate commands. + EXPLAIN ANALYZE statements are also logged if their + contained command is of an appropriate type. - The default is none. Only superusers can reduce - the detail of this option if it has been set by an administrator. + The default is none. Only superusers can change this + setting. - The EXECUTE statement not considered a + The EXECUTE statement is not considered a ddl or mod statement. When it is logged, only the name of the prepared statement is reported, not the actual prepared statement. - When a function is defined in a server-side language like - PL/pgSQL, any queries executed by - the function will only be logged the first time that the + When a function is defined in the + PL/pgSQLserver-side language, any queries + executed by the function will only be logged the first time that the function is invoked in a particular session. This is because - the PL/pgSQL keeps a cache of the + PL/pgSQL keeps a cache of the query plans produced for the SQL statements in the function. @@ -2556,11 +2554,10 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Win32 For each query, write performance statistics of the respective module to the server log. This is a crude profiling instrument. log_statement_stats reports total - statement statistics, while the others report per-state statistics. - log_statement_stats can not be enabled with - the other options. All of these options are disabled by default. - Only superusers can turn off any of these options if they have - been enabled by the administrator. + statement statistics, while the others report per-module statistics. + log_statement_stats cannot be enabled together with + any of the per-module options. All of these options are disabled by + default. Only superusers can change these settings. -- cgit v1.2.3