X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C77069DC827 for ; Fri, 20 Jan 2006 02:10:34 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 13630-10 for ; Fri, 20 Jan 2006 02:10:34 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 9A17D9DC804 for ; Fri, 20 Jan 2006 02:10:32 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k0K6AUYr013418; Fri, 20 Jan 2006 01:10:30 -0500 (EST) To: Scott Marlowe cc: "Jim C. Nasby" , pgsql-docs@postgresql.org Subject: Re: vacuum and routine maintenance docs In-reply-to: <1137711094.25500.152.camel@state.g2switchworks.com> References: <1137518049.25500.27.camel@state.g2switchworks.com> <20060117224941.GI17896@pervasive.com> <1137538769.25500.49.camel@state.g2switchworks.com> <20060118221951.GT17896@pervasive.com> <1137626008.25500.90.camel@state.g2switchworks.com> <5713.1137632107@sss.pgh.pa.us> <20060119011422.GM17896@pervasive.com> <5896.1137633556@sss.pgh.pa.us> <20060119013134.GR17896@pervasive.com> <1137687319.25500.129.camel@state.g2switchworks.com> <20060119220041.GG78403@pervasive.com> <1137711094.25500.152.camel@state.g2switchworks.com> Comments: In-reply-to Scott Marlowe message dated "Thu, 19 Jan 2006 16:51:34 -0600" Date: Fri, 20 Jan 2006 01:10:30 -0500 Message-ID: <13417.1137737430@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.094 required=5 tests=[AWL=0.094] X-Spam-Score: 0.094 X-Spam-Level: X-Archive-Number: 200601/49 X-Sequence-Number: 3439 Scott Marlowe writes: > Yeah, I keep thinking more and more we need a LOT of linkable resources > for this, much like the ones we have for all the standard command > reference stuff. I'm leaning towards having the main page of each of > these things be somewhat closer to an executive summary (not that light > on info, but you know what I mean) and have links to more info for each > subject. So that each section can have a much more in depth coverage > but not make it a huge slog to get through the documentation. The refrain that I keep hearing is that the info is in there but it's not so easy to find. So this sounds like a plan to me: quick overviews with links should make it easier to find the parts people need to read. regards, tom lane