Kevin Burke

@danielstjules would love this!

(I should add I'm not sure how to get the CLI to parse the timestamp as UTC besides passing in the whole thing, e.g. `--min-time='2016-05-16T16:03:00-00:00'`. I tried '16:03:00 UTC', '16:03:00-00:00'...

sweet. how do you imagine this looking? happy to help out, but if you're gonna do it go for it. On Fri, Jan 30, 2015 at 1:25 PM, Hunter Loftis...

That would give absolute timestamps, might be nice to have relative timestamps (this is how long this build step took) but that requires storing state. Maybe absolute is a good...

It looks like the pg-parsing library whitelists keys and probably also should be updated.

Sorry - parse-connection-string or some such.

See the "TimeZone" setting here: http://www.postgresql.org/docs/9.4/static/runtime-config-client.html > Sets the time zone for displaying and interpreting time stamps. The built-in default is GMT, but that is typically overridden in postgresql.conf; initdb...

(or any of those settings)

> Why try overriding this? Set the value in that file, and that's it. I manage the development environments for about 20 developers, any one of which may have misconfigured...

We're blocked on using native bindings because of https://github.com/brianc/node-postgres/issues/972. Furthermore, that wouldn't help with any of the other settings - say the statement_timeout or lock_timeout or default_isolation_level, which I imagine...