| From: | nunks <nunks(dot)lol(at)gmail(dot)com> |
|---|---|
| To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: A question regarding postgresql log messages, |
| Date: | 2019-03-21 15:26:08 |
| Message-ID: | CACq6szRkbnkoYb+LmWoVX98EEdzbLqbqUyoBrZNRmyriA-L2OQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Maybe you can use an informative log_line_prefix configuration, like
the proposed pg_badger one:
'%t [%p]: [%l-1] user=%u,db=%d,app=%a,client=%h '
This should give you more information about the real importance of the
error message to your use case. A FATAL error from user "postgres" or
"[unknown]" can be potentially more problematic than an error from
"user1". Also, postmaster messages won't have any of these variables
set:
2019-03-21 12:21:32 -03 [1714]: [17-1] user=,db=,app=,client= LOG:
checkpoint starting: time
--
----------
“Life beats down and crushes the soul and art reminds you that you have one.”
- Stella Adler
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Jane | 2019-03-21 15:47:33 | Re: Running postgresql databases in Docker |
| Previous Message | Evan Bauer | 2019-03-21 15:10:25 | Re: Running postgresql databases in Docker |