Re: autovacuum and reloptions - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: autovacuum and reloptions
Date
Msg-id 87d4ibqdc9.fsf@oxford.xeocode.com
Whole thread Raw
In response to autovacuum and reloptions  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: autovacuum and reloptions
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:

> Before we waste too much time thinking how this registering is to be
> done, does anybody think that the current approach is OK and thus I
> should just add the autovacuum options directly into StdRdOptions and
> default_reloptions?

Given Simon's suggestion that i/o parameters should be per-tablespace I think
we might need to refactor this further.

I wonder if we could piggy-back on guc parameters. So you would register a guc
variable with a flag saying it's sensible to be set per-tablespace or
per-table. 

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's PostGIS support!


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: autovacuum and reloptions
Next
From: Tom Lane
Date:
Subject: CREATE DATABASE vs delayed table unlink