| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Custom timestamp format in logs |
| Date: | 2014-12-13 14:50:44 |
| Message-ID: | CAB7nPqQMONc6CVx5j3zxQwyBf+RRsahn1shOF0PXmq5Ss+CgQA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
This week, we heard about a user willing to use a custom timestamp
format across a set of services to improve the debugability of the
whole set, Postgres being one of them. Unfortunately datestyle does
not take into account the logs. Would it be worth adding a new GUC
able to control the timestamp format in the logs?
We could still redirect the logs with syslog and have a custom
timestamp format there, but in the case of this particular user syslog
was a no-go. Looking at the code, timestamp format is now hardcoded in
setup_formatted_log_time and setup_formatted_start_time when calling
pg_strftime @ elog.c, so it doesn't seem to be much complicated to do.
Opinions? This thread is here for that.
Regards,
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2014-12-13 14:53:11 | Re: [TODO] Track number of files ready to be archived in pg_stat_archiver |
| Previous Message | Mark Dilger | 2014-12-13 14:45:57 | duplicate #define |