Re: autovacuum and reloptions
От | Robert Haas |
---|---|
Тема | Re: autovacuum and reloptions |
Дата | |
Msg-id | 603c8f070901101833j3f5e52daxf54414e2dd6f51b3@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: autovacuum and reloptions (Euler Taveira de Oliveira <euler@timbira.com>) |
Ответы |
Re: autovacuum and reloptions
|
Список | pgsql-hackers |
> Here is the patch that replace pg_autovaccum catalog with reloptions. I > refactored the reloptions.c to support multiple parameters and made the > action of adding a new option an easy task. I'm testing it yet, so don't > expect it to work properly. I'll prepare docs as soon as I finish the > tests. Do i have to prepare some regression tests? > > I don't provide a pg_autovacuum view as suggested by Itagari-san [1] but > if others agree that we need it, I will work on it. I don't if we need a > function (wrapper around getRelOption()) to get an option from > reloptions array. > > I add an ugly-hack to \d+ foo. IMHO, it'll be good to know what options > are used by table/index foo (we already do it for oids) but I'm not > happy with my suggestion. > > I move RelationGet*() functions from rel.h. That's because we need some > knowledge that's only in reloptions.c (getRelOptions). But I want to > avoid including reloptions.h at some files. > > Comments? > > PS> don't forget to remove include/catalog/pg_autovacuum.h Several things related to this patch have been committed: http://archives.postgresql.org/message-id/20081219143958.6F2DD7563FE@cvs.postgresql.org http://archives.postgresql.org/message-id/20090105171428.77B29754A17@cvs.postgresql.org (and several follow-on commits) What still remains to be done for 8.4? ...Robert
В списке pgsql-hackers по дате отправления: