Re: [HACKERS] Reporting xmin from VACUUMs
От | Jim Nasby |
---|---|
Тема | Re: [HACKERS] Reporting xmin from VACUUMs |
Дата | |
Msg-id | 1d9ce8ed-685b-ef96-34b2-345dc445c846@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Reporting xmin from VACUUMs (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Reporting xmin from VACUUMs
|
Список | pgsql-hackers |
On 2/15/17 12:05 PM, Alvaro Herrera wrote: > Jim Nasby wrote: >> ISTR previous discussion of allowing more stats files; if that happened >> I think having stats that were dedicated to (auto)vacuum would be very >> useful. That's clearly a lot more work though. > > What? There's a bunch of information reported by vacuum logging but not in pg_stat*, such as all-visible/frozen skipping, unable to get cleanup lock, last freeze scan, times autovac has been interrupted. There's been resistance in the past to further bloating the existing stats files, but if we allowed more than one stats file per database that bloat would be less of a concern (since vacuum stats will see far less update traffic than the main relation stats). -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532)
В списке pgsql-hackers по дате отправления: