Timeline for PostgreSQL bug(?) - logging with a minimum log level
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10, 2015 at 13:07 | comment | added | Erdinc Ay | I do understand your comment, and I also know the PostgreSQL article to this topic, but where is the LOGIC, which config counts first, which ORDER is being used to trigger, filter, write the logs? I can't imagine that all these people have an execution plan for PostgreSQL in their brains. | |
| Aug 7, 2015 at 11:23 | comment | added | Daniel Vérité | @ErdincAy Logging only when errors occur is the default configuration. For your questions there's an entire doc page about it, please read it: postgresql.org/docs/current/static/runtime-config-logging.html | |
| Aug 7, 2015 at 11:05 | comment | added | Erdinc Ay | yes i had to turn that to all, but there is no other granularity for statements, i need them, but only if errors occur, i thought maybe log_min_message can trigger when statements are logged, will have to test it next week, by the way, is there anyone that knows in which order and how the evaluation of the log configurations is done? | |
| Aug 7, 2015 at 10:10 | history | answered | Daniel Vérité | CC BY-SA 3.0 |