Difference between revisions of "Log statement"

From wikieduonline
Jump to navigation Jump to search
 
(10 intermediate revisions by 2 users not shown)
Line 3: Line 3:
  
 
  [[ALTER USER]] interactive_user SET log_statement = 'all';
 
  [[ALTER USER]] interactive_user SET log_statement = 'all';
 +
 +
[[SET SESSION]] log_statement TO 'all';
 +
 +
[[ALTER SYSTEM SET]] log_statement = 'all';
 +
[[ALTER USER]] application_user SET log_statement = 'none';
 +
 +
https://www.postgresql.org/docs/current/runtime-config-logging.html
 +
Controls which SQL statements are logged. Valid values are none (off), ddl, mod, and all (all statements). ddl logs all data definition
 +
statements, such as CREATE, ALTER, and DROP statements. mod logs all ddl statements, plus data-modifying statements such as INSERT,
 +
UPDATE, DELETE, TRUNCATE, and COPY FROM. PREPARE, EXECUTE, and EXPLAIN ANALYZE statements are also logged if their contained command is
 +
of an appropriate type. For clients using extended query protocol, logging occurs when an Execute message is received, and values of the
 +
Bind parameters are included (with any embedded single-quote marks doubled).
 +
 +
The default is none. Only superusers can change this setting.
 +
  
 
== Related ==
 
== Related ==
* [[/etc/postgresql/12/main/postgresql.conf]]
+
* [[AWS RDS query logging]], <code>[[log_min_duration_statement]]</code>
 +
* <code>[[/etc/postgresql/12/main/postgresql.conf]]</code>
 +
* Read https://www.cybertec-postgresql.com/en/debugging-deadlocks-in-postgresql/
  
 
== See also ==
 
== See also ==
 +
* {{aws rds parameter-group}}
 
* {{PostgreSQL}}
 
* {{PostgreSQL}}
  
 
[[Category:PostgreSQL]]
 
[[Category:PostgreSQL]]

Latest revision as of 08:31, 11 October 2022

#log_statement = 'none'			# none, ddl, mod, all
ALTER USER interactive_user SET log_statement = 'all';
SET SESSION log_statement TO 'all'; 
ALTER SYSTEM SET log_statement = 'all';
ALTER USER application_user SET log_statement = 'none';

https://www.postgresql.org/docs/current/runtime-config-logging.html

Controls which SQL statements are logged. Valid values are none (off), ddl, mod, and all (all statements). ddl logs all data definition 
statements, such as CREATE, ALTER, and DROP statements. mod logs all ddl statements, plus data-modifying statements such as INSERT, 
UPDATE, DELETE, TRUNCATE, and COPY FROM. PREPARE, EXECUTE, and EXPLAIN ANALYZE statements are also logged if their contained command is 
of an appropriate type. For clients using extended query protocol, logging occurs when an Execute message is received, and values of the 
Bind parameters are included (with any embedded single-quote marks doubled).

The default is none. Only superusers can change this setting.


Related[edit]

See also[edit]

Advertising: