On 05/28/2013 04:13 PM, Fabien COELHO wrote: > > You can try to use and improve the --progress option in another patch > submission which shows how things are going. That'll certainly be useful, but won't solve this issue. The thing is that with asynchronous replication you need to know how long it takes until all nodes are back in sync, with no replication lag.
I can probably do it with a custom pgbench script, but I'm tempted to add support for timing that part separately with a "wait command" to run at the end of the benchmark. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
