| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, <fabriziomello(at)gmail(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Publish autovacuum informations |
| Date: | 2016-03-01 21:30:37 |
| Message-ID: | 56D609FD.1040305@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/1/16 3:02 PM, Julien Rouhaud wrote:
> You mean for database wide vacuum?
I mean manual vacuum. Some hooks and stats would apply only to autovac
obviously (and it'd be nice to get visibility into the scheduling
decisions both daemons are making). But as much as possible things
should be done in vacuum.c/lazyvacuum.c so it works for manual vacuums
as well.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2016-03-01 21:31:19 | Re: pg_dump / copy bugs with "big lines" ? |
| Previous Message | Jim Nasby | 2016-03-01 21:23:27 | Re: Improve error handling in pltcl |