Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5AGBYE72428 for ; Sun, 10 Jun 2001 12:11:34 -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 f5AGBJo20990; Sun, 10 Jun 2001 12:11:19 -0400 (EDT) To: Stephan Szabo cc: Christophe Labouisse , pgsql-sql@postgresql.org Subject: Re: Integrity and Inheritance In-reply-to: References: Comments: In-reply-to Stephan Szabo message dated "Sat, 09 Jun 2001 22:23:58 -0700" Date: Sun, 10 Jun 2001 12:11:19 -0400 Message-ID: <20987.992189479@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200106/145 X-Sequence-Number: 3366 Stephan Szabo writes: > One problem is that for update isn't supported across inheritance trees > AFAICS and the triggers use for update for the appropriate locking. It's possible (maybe even likely) that this could be fixed with minimal work. I punted on it for 7.1 due to lack of time. However, is that really the major obstacle in the way of inherited foreign keys? Seems like there are a bunch of issues that'd require cross-table unique indexes, as well. regards, tom lane