Re: pgbench throttling latency limit

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, 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-13 08:25:05
Message-ID: alpine.DEB.2.10.1409131019470.29881@sto
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

> [about logging...]

Here is an attempt at updating the log features, including the aggregate
and sampling stuff, with skipped transactions under throttling.

I moved the logging stuff into a function which is called when a
transaction is skipped or finished.

From a log file format perspective, I think that "-" would be better than


Attachment Content-Type Size
pgbench-limit-9.patch text/x-diff 26.8 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2014-09-13 08:45:41 Re: documentation update for doc/src/sgml/func.sgml
Previous Message Костя Кузнецов 2014-09-13 08:19:43 Re: gist vacuum seaq access