Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAIJRJm93570 for ; Sun, 18 Nov 2001 14:27:20 -0500 (EST) (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.4/8.11.4) with ESMTP id fAIJQlc03572; Sun, 18 Nov 2001 14:26:47 -0500 (EST) To: "Aasmund Midttun Godal" cc: pgsql-sql@postgresql.org Subject: Re: System catalogs In-reply-to: <20011118184303.10663.qmail@ns.krot.org> References: <20011118184303.10663.qmail@ns.krot.org> Comments: In-reply-to "Aasmund Midttun Godal" message dated "Sun, 18 Nov 2001 18:43:03 +0000" Date: Sun, 18 Nov 2001 14:26:46 -0500 Message-ID: <3567.1006111606@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200111/257 X-Sequence-Number: 5639 "Aasmund Midttun Godal" writes: > I saw in the docs that you are not supposed to edit them manually... However is it considered appropriate to do other things such as: > referencing them (adding foreign keys on them) > adding triggers to them (e.g. delete all this stuff if this table is dropped). This would include adding cascade clauses to the referring. By and large, triggers on system catalogs will not work, because most of the internal manipulations of the catalogs do not bother to fire triggers. This implies that foreign key constraints won't work either, since those are implemented by triggers. regards, tom lane