| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Log timestamps at higher resolution |
| Date: | 2018-10-23 23:46:47 |
| Message-ID: | 20181023234647.GF1658@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Oct 24, 2018 at 12:11:18AM +0200, David Fetter wrote:
> That's an interesting point. pgbadger is the only one I recall using
> that's still maintained. Which others would it be useful to test?
There could be private solutions as well. My take is that we should use
separate letters and not change the existing ones or we'll get
complains.
> Also, do we have tests--or at least ideas of how to
> test--functionality relating to logging? I was a little bit taken
> aback by the fact that `make check-world` passed after the change.
This requires server-level changes where a TAP test is usually adapted,
and there is no test for logging yet.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-10-23 23:49:01 | Re: Buildfarm failures for hash indexes: buffer leaks |
| Previous Message | Michael Paquier | 2018-10-23 23:43:05 | Re: [PATCH] Tab complete EXECUTE FUNCTION for CREATE (EVENT) TRIGGER |