Re: Per-tablespace autovacuum settings

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Oleksii Kliukin <alexk(at)hintbits(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Travers <chris(dot)travers(at)adjust(dot)com>
Subject: Re: Per-tablespace autovacuum settings
Date: 2019-05-03 17:01:38
Message-ID: CA+TgmoYn0=zXEeR+gjKHGwF8RUWtWTu00qvEJb5DPCiYMwi0rg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Apr 25, 2019 at 12:36 PM Oleksii Kliukin <alexk(at)hintbits(dot)com> wrote:
> - Fallbacks to autovacuum parameters in another scope. Right now in the
> absence of the per-table and per-tablespace autovacuum parameters the code
> uses the ones from the global scope. However, if only some of the reloptions
> are set on a per-table level (i.e. none of the autovacuum related ones), we
> assume defaults for the rest of reloptions without consulting the lower
> level (i.e .per-tablespace options). This is so because we don’t have the
> mechanism to tell whether the option is set to its default value (some of
> them use -1 to request the fallback to the outer level, but for some it’s
> not possible, i.e. autovacuum_enabled is just a boolean value).

That sounds like it's probably not acceptable?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Wong 2019-05-03 17:08:59 Re: Why is infinite_recurse test suddenly failing?
Previous Message Tom Lane 2019-05-03 16:21:36 Re: error messages in extended statistics