Re: Publish autovacuum informations - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Publish autovacuum informations
Date
Msg-id CA+TgmoYxtr1rOHSaxn43MUqrwPqZcXVjnkR3fq8SK6cG4BjJKA@mail.gmail.com
Whole thread Raw
In response to Re: Publish autovacuum informations  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Publish autovacuum informations  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Dec 29, 2014 at 11:03 AM, Tom Lane <tgl@sss.pgh.pa.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



pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Parallel Seq Scan
Next
From: Alvaro Herrera
Date:
Subject: Re: Failure on markhor with CLOBBER_CACHE_ALWAYS for test brin