Re: autovacuum and reloptions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: autovacuum and reloptions
Date: 2008-10-09 12:47:08
Message-ID: 13123.1223556428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> writes:
> Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> So I gave up waiting for someone else to do the reloptions patch for
>> autovacuum and started work on it myself.

> Is it needed to keep backward compatibility?

> I'd like to suggest to keep pg_catalog.pg_autovacuum as a system view
> even after the options is put into reloptons, and the view to be
> updatable using RULEs if possible.

Ugh. No. It has been explicitly stated all along that pg_autovacuum
was a temporary API and that anyone depending on it could expect future
trouble.

> But we will not able to do that if the settings will be in reloptions
> because ALTER TABLE SET cannot be used with JOINs.

Any mechanism that a rule might use to set reloptions would be just
as usable in a join as the rule itself ...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthew Wakeling 2008-10-09 12:50:07 Re: CREATE DATABASE vs delayed table unlink
Previous Message Tom Lane 2008-10-09 12:42:55 Re: About postgresql8.3.3 build in MS VS2005