| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Jan Wieck <jan(at)wi3ck(dot)info>, Rukh Meski <rukh(dot)meski(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench throttling latency limit |
| Date: | 2014-09-12 19:28:15 |
| Message-ID: | CA+Tgmoai-Mk0aooXtq2cCCTkpY_b7exo_AWTGH54eteJdLaN8A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 12, 2014 at 2:27 PM, Gregory Smith <gregsmithpgsql(at)gmail(dot)com> wrote:
> If there's a good case that the whole format needs to be changed anyway,
> like adding a new field, then we might as well switch to fractional epoch
> timestamps too now though. When I added timestamps to the latency log in
> 8.3, parsers that handled milliseconds were even more rare. Today it's
> still inconsistent, but the workarounds are good enough to me now. There's
> a lot more people using things like Python instead of bash pipelines here in
> 2014 too.
+1. s/\..*// is not an onerous requirement.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-09-12 19:38:01 | Re: [REVIEW] Re: Compression of full-page-writes |
| Previous Message | Jeff Janes | 2014-09-12 19:17:03 | Re: pgcrypto: PGP signatures |