| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: autovacuum and reloptions |
| Date: | 2008-10-08 16:08:22 |
| Message-ID: | 87d4ibqdc9.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-10-08 16:08:55 | CREATE DATABASE vs delayed table unlink |
| Previous Message | Tom Lane | 2008-10-08 15:34:40 | Re: autovacuum and reloptions |