Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tomas Vondra <tv@fuzzy.cz>, pgsql-hackers@postgresql.org
Date: 2013-02-06T15:40:50Z
Lists: pgsql-hackers
Pavel Stehule <pavel.stehule@gmail.com> writes:
>> Nice. Another interesting numbers would be device utilization, average
>> I/O speed and required space (which should be ~2x the pgstat.stat size
>> without the patch).

> this point is important - with large warehouse with lot of databases
> and tables you have move stat file to some ramdisc - without it you
> lost lot of IO capacity - and it is very important if you need only
> half sized ramdisc

[ blink... ]  I confess I'd not been paying close attention to this
thread, but if that's true I'd say the patch is DOA.  Why should we
accept 2x bloat in the already-far-too-large stats file?  I thought
the idea was just to split up the existing data into multiple files.

			regards, tom lane


Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Split pgstat file in smaller pieces