Got it...
It seams those triggers were created to handle the types I used for the
columns: int2 and bytea...
I realy should check out the types section in the postgres docu :))
> -----Original Message-----
> From: Gregory Wood [mailto:gregw@com-stock.com]
> Sent: Thursday, April 26, 2001 7:59 PM
> To: Christian Marschalek
> Cc: PostgreSQL-General
> Subject: Re: NOTICE: CREATE TABLE will create implicit
> trigger(s) for FOREIGN KEY check(s) ?
>
>
> > Can anyone tell me what this notice means?
> >
> > NOTICE: CREATE TABLE will create implicit trigger(s) for
> FOREIGN KEY
> > check(s) ?
>
> It means that PostgreSQL will automatically create triggers
> to perform your foreign key checks :)
>
> Seriously though, PostgreSQL has to have some mechanism to
> check that your foreign key values exist (or not), and it
> does that by using a feature already built into PostgreSQL:
> triggers. Nothing you really need to worry about unless you
> are doing something fancy (for instance, disabling all
> triggers on either table to accomplish some action... in such
> a case your foreign key relationship might be broken).
>
> Greg
>
>
