Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
P
postgres-lambda-diff
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Jakob Huber
postgres-lambda-diff
Commits
8f6e8e8f
Commit
8f6e8e8f
authored
19 years ago
by
Bruce Momjian
Browse files
Options
Downloads
Patches
Plain Diff
Clarify documentation about log_min_duration_statement.
parent
53502161
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/src/sgml/runtime.sgml
+12
-11
12 additions, 11 deletions
doc/src/sgml/runtime.sgml
src/backend/utils/misc/postgresql.conf.sample
+2
-1
2 additions, 1 deletion
src/backend/utils/misc/postgresql.conf.sample
with
14 additions
and
12 deletions
doc/src/sgml/runtime.sgml
+
12
−
11
View file @
8f6e8e8f
<!--
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.33
2
2005/0
6/26 19:16:04 tgl
Exp $
$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.33
3
2005/0
7/01 13:29:23 momjian
Exp $
-->
<chapter Id="runtime">
...
...
@@ -2628,16 +2628,17 @@ archive_command = 'copy "%p" /mnt/server/archivedir/"%f"' # Windows
</indexterm>
<listitem>
<para>
Sets a minimum statement execution time (in milliseconds)
that causes a statement to be logged. All SQL statements
that run for the time specified or longer will be logged with
their duration. Setting this to zero will print
all queries and their durations. Minus-one (the default)
disables the feature. For example, if you set it to
<literal>250</literal> 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 change this setting.
Logs the statement and its duration on a single log line if its
duration is greater than or equal to the specified number of
milliseconds. Setting this to zero will print all statements
and their durations. Minus-one (the default) disables the
feature. For example, if you set it to <literal>250</literal>
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. This setting is
independent of <varname>log_statement</varname> and
<varname>log_duration</varname>. Only superusers can change
this setting.
</para>
</listitem>
</varlistentry>
...
...
This diff is collapsed.
Click to expand it.
src/backend/utils/misc/postgresql.conf.sample
+
2
−
1
View file @
8f6e8e8f
...
...
@@ -227,7 +227,8 @@
# debug5, debug4, debug3, debug2, debug1,
# info, notice, warning, error, panic(off)
#log_min_duration_statement = -1 # -1 is disabled, in milliseconds.
#log_min_duration_statement = -1 # -1 is disabled, 0 logs all statements
# and their durations, in milliseconds.
#silent_mode = false # DO NOT USE without syslog or redirect_stderr
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment