Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4IFFKA19058 for ; Fri, 18 May 2001 11:15:21 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.3/8.11.3) with ESMTP id f4IFFCR15698; Fri, 18 May 2001 11:15:13 -0400 (EDT) To: Florian Weimer cc: pgsql-sql@postgresql.org Subject: Re: Inherited tables: How stable is that feature? In-reply-to: References: Comments: In-reply-to Florian Weimer message dated "18 May 2001 10:13:15 +0200" Date: Fri, 18 May 2001 11:15:12 -0400 Message-ID: <15695.990198912@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/199 X-Sequence-Number: 3016 Florian Weimer writes: > Is it likely that table inheritance is going to be removed in future > PostgreSQL versions (or that the semantics change radically)? I doubt anyone is planning to remove it. If anything it'll get better supported. Notice that 7.1 now allows update/delete over inheritance hierarchies, which never worked before --- that doesn't look like a dying feature to me. I would not really recommend using multiple inheritance, but single inheritance seems like a safe-enough bet. regards, tom lane