Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.8.8/8.7.5) with ESMTP id MAA12549 for ; Thu, 9 Jul 1998 12:47:10 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id MAA02429 for ; Thu, 9 Jul 1998 12:47:08 -0400 (EDT) To: pgsql-sql@postgresql.org Subject: Indexes and inheritance (and access rights) Date: Thu, 09 Jul 1998 12:47:08 -0400 Message-ID: <2426.900002828@sss.pgh.pa.us> From: Tom Lane If I have a collection of tables related by inheritance, is there any (forced or optional) relationship between indexes on those tables? For example, if I have a table A with an index Ai, and I create table B that INHERITS (A), do I automatically get an index Bi on B with the same properties as Ai? (For that matter, if it's *not* automatic, can I make it happen somehow? I'd like the index structure of a table to be part of its class definition, in essence.) Is there a way to make a single index that indexes records in both A and B? (For example, to enforce uniqueness of a particular field globally across A and all its inheritors.) While I'm on about indexes: it seems I can GRANT or REVOKE access rights on an index, but what the heck does that mean? Are access rights on an index actually checked when doing operations on the underlying table? It would seem rather confusing to do that. regards, tom lane