Re: pg_dump issue : Cannot drop a non-existent(?) trigger

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

On Fri, 25 Mar 2005, Stephan Szabo wrote:

>> =======================================================================
>> prod=# \d t_firma_moduller
>> Table
>> "public.t_firma_moduller"
>> Column | Type |
>> Modifiers
>> - ------------------+-----------------------------+--------------------------------------------------------------------------
>> firma_no | character varying(10) | not null
>> modul_adi | character varying(20) | not null
>> last_update_date | timestamp without time zone |
>> last_update_user | character varying(45) |
>> kod | integer | not null default
>> fn_get_seq_value('t_firma_moduller'::character varying)
>> Indexes:
>> "t_firma_moduller_pkey" PRIMARY KEY, btree (firma_no, modul_adi)
>> "t_firma_moduller_kodu_ukey" UNIQUE, btree (kod)
>> Triggers:
>> "RI_ConstraintTrigger_39053" AFTER INSERT OR UPDATE ON
>> t_firma_moduller FROM t_firmalar NOT DEFERRABLE INITIALLY IMMEDIATE FOR
>> EACH ROW EXECUTE PROCEDURE
>> "RI_FKey_check_ins"('firma_moduller_firma_fkey1', 't_firma_moduller',
>> 't_firmalar', 'UNSPECIFIED', 'firma_no', 'no')
>
> Odd, why is this not showing up as a foreign key constraint? Has this
> database been upgraded (no matter through how many different upgrades)
> from an old version (7.1 or earlier I think)?

No, this is a fresh install. The database went live about 1 month ago.

>> prod=# DROP TRIGGER RI_ConstraintTrigger_39053 ON t_firma_moduller;
>> ERROR: trigger "ri_constrainttrigger_39053" for table "t_firma_moduller"
>> does not exist
>
> You'd need to quote the trigger name because it's mixed case.

:-( I should have thought it. Thanks.

>> Is this a bug or something? There should not be a trigger there.
>
> Well, it really should be showing up as something like:
> CONSTRAINT firma_moduller_firma_fkey1 FOREIGN KEY (firma_no)
> REFERENCES t_firmalar(no)

The problem is:

* We ran pg_dump about 15 days before with no problem. Neither any data
nor any relation was dropped since the cluster was initialized. If the
trigger was there, how could we run pg_dump successfully? If it isn't
there, why does it prevent pg_dump?

Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org, devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.tdmsoft.com http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFCRCpPtl86P3SPfQ4RAjJCAJ9RuDrfeS78cNlJABvybhori6Cm6ACgtaxr
p79z+3ty4SFTDnlaUK+ZdUM=
=vaRH
-----END PGP SIGNATURE-----