| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Publish autovacuum informations |
| Date: | 2014-12-31 16:19:52 |
| Message-ID: | CA+TgmoYxtr1rOHSaxn43MUqrwPqZcXVjnkR3fq8SK6cG4BjJKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 29, 2014 at 11:03 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Either one of those approaches would cripple our freedom to change those
> data structures; which we've done repeatedly in the past and will surely
> want to do again. So I'm pretty much -1 on exposing them.
We could instead add a view of this information to core --
pg_stat_autovacuum, or whatever.
But to be honest, I'm more in favor of Guillaume's proposal. I will
repeat my recent assertion that we -- you in particular -- are too
reluctant to expose internal data structures to authors of C
extensions, and that this is developer-hostile.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-12-31 16:21:55 | Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin |
| Previous Message | Thom Brown | 2014-12-31 16:16:20 | Re: Parallel Seq Scan |