Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T4Y6l-0003S6-NG for pgsql-docs@postgresql.org; Thu, 23 Aug 2012 14:10:03 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1T4Y6g-0005ik-RK for pgsql-docs@postgresql.org; Thu, 23 Aug 2012 14:10:03 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q7NE9v2x011192; Thu, 23 Aug 2012 10:09:57 -0400 (EDT) From: Tom Lane To: Chris Travers cc: Postgres Documentation Subject: Re: Thoughts on inheritance docs In-reply-to: References: Comments: In-reply-to Chris Travers message dated "Wed, 22 Aug 2012 23:40:42 -0700" Date: Thu, 23 Aug 2012 10:09:57 -0400 Message-ID: <11191.1345730997@sss.pgh.pa.us> X-Pg-Spam-Score: -2.1 (--) X-Archive-Number: 201208/40 X-Sequence-Number: 7433 Chris Travers writes: > 1) Would it be worth coming up with more useful examples for table inheritance? > 2) Would it be worth adding mention of uses of multiple table inheritance? > 3) Would it be worth discussing how to position the limitations of > table inheritance? I personally recognize the difficulties in > documenting these but I can't help thinking that a simple chart of > "this is/is not inherited" would be very useful as well. All of those sound sane to me at this level of detail, and in particular I agree that the docs are short on examples of multiple inheritance. The arguments will probably start once you get more concrete ... regards, tom lane