X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 9C0D8D1D61F for ; Tue, 25 Nov 2003 04:21:45 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 27484-08 for ; Tue, 25 Nov 2003 00:21:17 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 585DAD1CAD1 for ; Tue, 25 Nov 2003 00:21:16 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id hAP4LGNu050445 for ; Tue, 25 Nov 2003 04:21:16 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id hAP4CTZT049017 for pgsql-performance@postgresql.org; Tue, 25 Nov 2003 04:12:29 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: [HACKERS] More detail on settings for pgavd? Date: Mon, 24 Nov 2003 23:08:08 -0500 Organization: cbbrowne Computing Inc Lines: 38 Message-ID: References: <200311181558.45847.josh@agliodbs.com> <1069424054.29672.12462.camel@camel> <3FBE21D5.20508@zeut.net> <200311210909.00978.josh@agliodbs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Reasonable Discussion, linux) Cancel-Lock: sha1:XUF1rnSlb/8Axa0fuCtewYQLVvk= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=QUOTED_EMAIL_TEXT, RCVD_IN_OSIRUSOFT_COM, REFERENCES, USER_AGENT_GNUS_UA X-Spam-Level: X-Archive-Number: 200311/237 X-Sequence-Number: 4797 After a long battle with technology, josh@agliodbs.com (Josh Berkus), an earthling, wrote: >> As long as pg_autovacuum remains a contrib module, I don't think >> any changes to the system catelogs will be make. If pg_autovacuum >> is deemed ready to move out of contrib, then we can talk about the >> above. > > But we could create a config file that would store stuff in a > flatfile table, OR we could add our own "system table" that would be > created when one "initializes" pg_avd. The problem with introducing a "config file" is that you then have to introduce a language and a parser for that language. That introduces rather a lot of complexity. That was the BIG problem with pgavd (which is a discarded project; pg_autovacuum is NOT the same thing as pgavd). There was more code involved just in managing the pgavd parser than there is in all of pg_autovacuum. I think the right answer for more sophisticated configuration would involve specifying a database in which to find the pg_autovacuum table(s). > Just an idea. Mind you, I'm not so sure that we want to focus > immediately on per-table settings. I think that we want to get the > "automatic" settings working fairly well first; a lot of new DBAs > would use the per-table settings to shoot themselves in the foot. > So we need to be able to make a strong recommendation to "try the > automatic settings first." Yeah, it's probably a good idea to ensure that per-table settings involves some really conspicuous form of "foot gun" (with no kevlar socks) to discourage its use except when you _know_ what you're doing... -- let name="cbbrowne" and tld="ntlug.org" in String.concat "@" [name;tld];; http://www3.sympatico.ca/cbbrowne/nonrdbms.html Q: Can SETQ only be used with numerics? A: No, SETQ may also be used by Symbolics, and use it they do.