Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tomas Vondra <tv@fuzzy.cz>
Cc: pgsql-hackers@postgresql.org
Date: 2013-02-19T22:31:17Z
Lists: pgsql-hackers
Tomas Vondra wrote: > AFAIK the stats remain the same within a transaction, and as a function > runs within a transaction, it will either get new data on the first > iteration, or it will run all 300 of them. I've checked several > buildfarm members and I'm yet to see a single duration between 12ms and > 30sec. No, there's a call to pg_stat_clear_snapshot() that takes care of that. > I'm really wondering how that could happen. The only thing that I can > think of is some strange timing issue, causing lost requests to write > the stats or maybe some of the stats updates. Hmmm, IIRC the stats are > sent over UDP - couldn't that be related? yes, UDP packet drops can certainly happen. This is considered a feature (do not cause backends to block when the network socket to stat collector is swamped; it's better to lose some stat messages instead). -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Split pgstat file in smaller pieces
- 187492b6c2e8 9.3.0 cited