From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
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-09 02:41:19 |
Message-ID: | 20081009113015.78FF.52131E4D@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
Current pg_autovacuum-table approach has a benefit that
we can configure options by rule, for example:
INSERT INTO pg_autovacuu SELECT ... FROM pg_class WHERE ...;
But we will not able to do that if the settings will be in reloptions
because ALTER TABLE SET cannot be used with JOINs.
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Dickson S. Guedes | 2008-10-09 02:58:38 | Re: WITH RECURSIVE ... simplified syntax? |
Previous Message | KaiGai Kohei | 2008-10-09 01:01:12 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1081) |