vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| All this thread is a waste of time. We've previously agreed that we're going to store autovacuum per-table settings in pg_class.reloptions. That automatically gives it pg_dump support, and moreover it means the user needs not set the options that he/she doesn't want to change from defaults. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
| |||
| Alvaro Herrera <alvherre@commandprompt.com> writes: > All this thread is a waste of time. We've previously agreed that we're > going to store autovacuum per-table settings in pg_class.reloptions. I had forgotten that discussion. So the plan is for the pg_autovacuum catalog to go away entirely, correct? regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| |||
| Tom Lane wrote: > Alvaro Herrera <alvherre@commandprompt.com> writes: > > All this thread is a waste of time. We've previously agreed that we're > > going to store autovacuum per-table settings in pg_class.reloptions. > > I had forgotten that discussion. So the plan is for the pg_autovacuum > catalog to go away entirely, correct? Yup. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| |||
| On Thursday 17 January 2008 19:17:00 Joshua D. Drake wrote: > On Thu, 17 Jan 2008 21:43:46 -0300 > > Alvaro Herrera <alvherre@commandprompt.com> wrote: > > Tom Lane wrote: > > > Alvaro Herrera <alvherre@commandprompt.com> writes: > > > > All this thread is a waste of time. We've previously agreed that > > > > we're going to store autovacuum per-table settings in > > > > pg_class.reloptions. > > > > > > I had forgotten that discussion. So the plan is for the > > > pg_autovacuum catalog to go away entirely, correct? > > > > Yup. > > Wait .reloptions is a column... how are we going to populate it and > array? ALTER TABLE foo SET autovacuum to true; ALTER TABLE foo SET autovacuum_naptime to '1min'; (or there about) I suppose we could also have pg_autovacuum become a view, with rules to manage relopts. > > Sincerely, > > Joshua D. Drake -- Darcy Buskermolen Command Prompt, Inc. +1.503.667.4564 X 102 http://www.commandprompt.com/ PostgreSQL solutions since 1997 ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| ||||
| Added to TODO: o Store per-table autovacuum settings in pg_class.reloptions. http://archives.postgresql.org/pgsql...2/msg01440.php http://archives.postgresql.org/pgsql...1/msg00724.php --------------------------------------------------------------------------- Alvaro Herrera wrote: > All this thread is a waste of time. We've previously agreed that we're > going to store autovacuum per-table settings in pg_class.reloptions. > That automatically gives it pg_dump support, and moreover it means the > user needs not set the options that he/she doesn't want to change from > defaults. > > -- > Alvaro Herrera http://www.CommandPrompt.com/ > PostgreSQL Replication, Consulting, Custom Development, 24x7 support > > ---------------------------(end of broadcast)--------------------------- > TIP 6: explain analyze is your friend -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers |