pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Sandy Spence <axs@aber.ac.uk>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: 'Rajesh Kumar Mallah' <mallah.rajesh@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Trigger trouble
Date: Wed, 3 Jan 2007 15:20:23 -0000
Message-ID: <008d01c72f4a$b3103e20$520b3cc1@pc2axs> (raw)
In-Reply-To: <23990.1166798369@sss.pgh.pa.us>

Hi Tom,

Thanks for the reply, sorry for the delay in responding a Scotsman and
Hogmanay are never parted ;~}

The version of postgres we are currently running is PostgreSQL 7.2.3

I did a Drop type trigger on the users database adding a tab at the end and
came up with the list below


RI_ConstraintTrigger_6081987  RI_ConstraintTrigger_6081995
RI_ConstraintTrigger_6082037  bestworkbehave
RI_ConstraintTrigger_6081989  RI_ConstraintTrigger_6081997
RI_ConstraintTrigger_6121610  pg_sync_pg_pwd
RI_ConstraintTrigger_6081991  RI_ConstraintTrigger_6082033
RI_ConstraintTrigger_6121612  tidyup 
RI_ConstraintTrigger_6081993  RI_ConstraintTrigger_6082035
RI_ConstraintTrigger_6121614

as you can see there appears to be an instance of a trigger that is not
connected to anything, is there a table that has an entry where I can remove
the offending trigger?

Cheers,

Sandy

Computer Officer, RA Certification Manager
Department of Computer Science - UWA
Llandinam Building
Penglais Campus
Aberystwyth
Ceredigion
Wales - UK
SY23 3DB
Tel: (01970)-622433
Fax: (01970)-628536


-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Tom Lane
Sent: 22 December 2006 14:39
To: Sandy Spence
Cc: 'Rajesh Kumar Mallah'; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Trigger trouble 

"Sandy Spence" <axs@aber.ac.uk> writes:
> select typowner from pg_type where typname='trigger';  typowner
> ----------
> (0 rows)

Um ... what PG version is this exactly?  ("select version()" if you're not
sure.)

It's real hard to see why pg_dump would complain about a type that's not
there at all.  You sure you checked this in the same database that's being
dumped?

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faq




view thread (10+ messages)  latest in thread

Message-ID: <008d01c72f4a$b3103e20$520b3cc1@pc2axs>
Permalink:  ../008d01c72f4a$b3103e20$520b3cc1@pc2axs/
Also on:    postgresql.org/message-id/008d01c72f4a$b3103e20$520b3cc1@pc2axs

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: axs@aber.ac.uk, tgl@sss.pgh.pa.us, mallah.rajesh@gmail.com
  Subject: Re: Trigger trouble
  In-Reply-To: <008d01c72f4a$b3103e20$520b3cc1@pc2axs>
  References: <23990.1166798369@sss.pgh.pa.us> <008d01c72f4a$b3103e20$520b3cc1@pc2axs>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox