[DOCS] TODO build rule
I tried building TODO.html from TODO according to the description in doc/src/FAQ/README, but saw the following kind of difference repeating: @@ -24,7 +24,7 @@ Administration - -Allow administrators to safely terminate individual sessions either + -Allow administrators to safely terminate individual sessions either via an SQL function or SIGTERM Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptly Apparently, there is a piece of code missing that adds these tags around the done items. Bruce, do you have this code, and can you add it to the README? -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [HACKERS] [DOCS] [ADMIN] shared_buffers and shmmax
Greg Smith wrote: > On Thu, 24 Jul 2008, Greg Sabino Mullane wrote: > > > Bite the bullet and start showing the buffer settings as a pure number of > > bytes > > everywhere, and get rid of the confusing '8kB' unit in pg_settings? > > There's already some changes needed in this area needed to execute the > full GUC cleanup/wizard plan that's being worked on. The pg_settings view > really should show the value both as the user input it and as it's stored > internally for cases like these, which lowers the confusion here a bit > even without going so far as converting everything to bytes. Is this a TODO? -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
Re: [HACKERS] [DOCS] [ADMIN] shared_buffers and shmmax
On Tue, 12 Aug 2008, Bruce Momjian wrote: There's already some changes needed in this area needed to execute the full GUC cleanup/wizard plan that's being worked on. The pg_settings view really should show the value both as the user input it and as it's stored internally for cases like these, which lowers the confusion here a bit even without going so far as converting everything to bytes. Is this a TODO? I don't think you need yet another TODO for every detail, the existing TODO "Add external tool to auto-tune some postgresql.conf parameters" has to squash a bunch of issues in this area. This particular issue Greg raised will already be improved significantly if executing the larger project plan at http://wiki.postgresql.org/wiki/GUCS_Overhaul This week Robert Treat and I have been doing a lot of work on "Problem #1" there, "Most people have no idea how to set [GUCs]" which I know some people wanted to see a more formal document for before mucking with any of the code. I'll have something to announce there shortly. -- * Greg Smith [EMAIL PROTECTED] http://www.gregsmith.com Baltimore, MD -- Sent via pgsql-docs mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs
