Re: [PATCH] add --throttle to pgbench (submission 3)

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Greg Smith <greg(at)2ndQuadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] add --throttle to pgbench (submission 3)
Date: 2013-05-31 07:41:09
Message-ID: alpine.DEB.2.02.1305310938440.31253@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> However I'm not sure that pg_stat_replication currently has the
>> necessary information on either side to measure the lag (in time
>> transactions, but how do I know when a transaction was committed? or
>> number of transactions?).
>
> The BDR codebase now has a handy function to report when a transaction
> was committed, pg_get_transaction_committime(xid) .

This looks handy for monitoring a replication setup.
It should really be in core...

Any plans? Or is there other ways to get this kind of information in core?

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2013-05-31 07:55:49 Re: 9.3: Empty arrays returned by array_remove()
Previous Message Brendan Jurd 2013-05-31 07:34:43 Re: 9.3: Empty arrays returned by array_remove()