Re: [DOCS] Added documentation about caching, reliability
On Wed, 2005-09-28 at 14:26 -0400, Bruce Momjian wrote: > I have added a section to the top of the WAL docs explaining caching and > reliability issues: > > http://candle.pha.pa.us/main/writings/pgsql/sgml/reliability.html > > I also renamed the chapter "Reilability" rather than "WAL." > I submitted a patch last week that builds further on Bruce's changes. [Docs for PITR and full_page_writes interaction, 2 Oct] The patch includes: 1. Minor rewording of the case that Bruce refers to "recovery" and I have differentiated the cases of crash recovery and PITR. The corresponding section of the backup chapter has also been changed to include a short discussion on full_page_writes and WAL compression, with a link back to the WAL section. 2. Merged the 1st and 2nd sects of Reliability into a single section. The 1st section was only a single paragraph and so that improves readability. I've freshened that section, since it has not been updated since 7.1 and currently still reads as if WAL has just been released. 3. I've updated the section on WAL configuration with further WAL related comments and clarifications. These relate to full_page_writes and appropriate settings of wal_buffers to match. Best Regards, Simon Riggs ---(end of broadcast)--- TIP 6: explain analyze is your friend
[DOCS] Inheritance and Partitioning
I'm currently doing the docs for CE & Partitioning. The ddl.sgml chapter had a section on Inheritance. I'm expanding that section and splitting it into two: INHERITANCE & PARTITIONING 1. Table Partitioning Existing chapter, but with more detail of a general nature that will be important information when we discuss... 2. Basic Partitioning using Constraint Exclusion How to enhance inheritance with constraints to allow CE. How that works to provide basic partitioning, with examples and long list of caveats. Any comments while I'm in progress? You will of course have another chance to comment when I complete the patch. Best Regards, Simon Riggs ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] Inheritance and Partitioning
Simon Riggs wrote: > I'm currently doing the docs for CE & Partitioning. > > The ddl.sgml chapter had a section on Inheritance. I'm expanding that > section and splitting it into two: > > INHERITANCE & PARTITIONING >1. Table Partitioning > Existing chapter, but with more detail of a general nature that > will be important information when we discuss... > >2. Basic Partitioning using Constraint Exclusion > How to enhance inheritance with constraints to allow CE. How that > works to provide basic partitioning, with examples and long list of > caveats. Hmm, sorry, I missed most of the discussion on CE -- is it used only in inheritance? Maybe you should add a separate section on partitioning, referring to the inheritance section where appropiate. But they are clearly not the same feature. Also, it will be more clearly separated as we add more partitioning related features, right? -- Alvaro Herrera Architect, http://www.EnterpriseDB.com "A wizard is never late, Frodo Baggins, nor is he early. He arrives precisely when he means to." (Gandalf, en LoTR FoTR) ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [DOCS] Inheritance and Partitioning
On Sun, 2005-10-09 at 10:56 -0300, Alvaro Herrera wrote: > Simon Riggs wrote: > > I'm currently doing the docs for CE & Partitioning. > > > > The ddl.sgml chapter had a section on Inheritance. I'm expanding that > > section and splitting it into two: > > > > INHERITANCE & PARTITIONING > >1. Table Partitioning > > Existing chapter, but with more detail of a general nature that > > will be important information when we discuss... > > > >2. Basic Partitioning using Constraint Exclusion > > How to enhance inheritance with constraints to allow CE. How that > > works to provide basic partitioning, with examples and long list of > > caveats. > > Hmm, sorry, I missed most of the discussion on CE -- is it used only > in inheritance? Regrettably at this time. I couldn't find a clear point to put the code that would allow it to work cleanly for the UNION ALL case, at least in the time available. > Maybe you should add a separate section on > partitioning, referring to the inheritance section where appropiate. > But they are clearly not the same feature. > > Also, it will be more clearly separated as we add more partitioning > related features, right? OK. I'll keep the same flow, just promote both up a level. So there'll be two s for each concept. Best Regards, Simon Riggs ---(end of broadcast)--- TIP 6: explain analyze is your friend
