Re: Can not pg_dumpall

From: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
To: Somazx Interesting <somazx(at)home(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Can not pg_dumpall
Date: 2001-06-08 20:30:51
Message-ID: Pine.BSF.4.21.0106081328240.26944-100000@megazone23.bigpanda.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Fri, 8 Jun 2001, Somazx Interesting wrote:

> At 02:18 PM 6/8/2001 -0400, Tom Lane wrote:
> >Somazx Interesting <somazx(at)home(dot)com> writes:
> > > getTables(): SELECT (funcname) for trigger sa_eval_trigger_608 returned 0
> > > tuples. Expected 1.
> > > pg_dump failed on OnEd, exiting
> >
> >Kinda looks like you dropped some function that was still referenced by
> >a trigger. Better drop the trigger too.
>
> Taking that to mean, "try deleting that orphaned trigger" - but since I
> don't know which table that trigger was on - I did it by deleting it
> through pg_trigger, I now get somewhat worse errors:
>
> getTables(): relation 'lessontable_548_118': 8 Triggers were expected, but
> got 7
>

This is easy to fix, actually. You need to change reltriggers on the
pg_class row for lessontable_548_118 to match the number of triggers that
are really there (7).

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2001-06-08 20:40:54 Re: Can not pg_dumpall
Previous Message Somazx Interesting 2001-06-08 19:46:33 Re: Can not pg_dumpall