Re: RFC: changing autovacuum_naptime semantics

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:

> > Is everybody OK with not putting a per-tablespace worker limit?
> > Is everybody OK with putting per-database worker limits on a pg_database
> > column?
>
> I don't think we need a new pg_database column. If it's a GUC you can
> do ALTER DATABASE SET, no? Or was that what you meant?

No, that doesn't work unless we save the datconfig column to the
pg_database flatfile, because it's the launcher (which is not connected)
who needs to read it. Same thing with an hypothetical per-database
naptime. The launcher would also need to parse it, which is not ideal
(though not a dealbreaker either).

--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.