Skip site navigation (1) Skip section navigation (2)

Re: NOTICE: CREATE TABLE will create implicit triggers for foreign-key checks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: NOTICE: CREATE TABLE will create implicit triggers for foreign-key checks
Date: 2003-10-01 14:31:22
Message-ID: 28993.1065018682@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Regarding the NOTICE
> CREATE TABLE will create implicit triggers for foreign-key checks
> Does anyone care?

I was thinking just the other day that it seemed to be useless clutter.

> The other "helpful" notices about sequences for serial columns and indexes
> for unique constraints have some merit, because they inform the user
> objects that the user might be interested in are going to be created as a
> side effect.

More to the point, they give the names of the automatically-created
objects.  If the FK trigger creation notice included the names of the
triggers then it might have nonzero value.  But I'm not sure that people
need to care anymore about the names of the triggers, since there's no
longer much reason to manipulate those triggers.  Nowadays you'd
manipulate the FK constraint itself, instead.

I'm in favor of dropping it...

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2003-10-01 14:44:57
Subject: Re: Thoughts on maintaining 7.3
Previous:From: Andreas Joseph KroghDate: 2003-10-01 14:00:08
Subject: Patch for allowing multiple -t <table-name> options for pg_dump

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group