Re: ERROR: could not find tuple for trigger 37463634

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: mdione(dot)ext(at)orange(dot)com
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: ERROR: could not find tuple for trigger 37463634
Date: 2012-03-07 15:12:22
Message-ID: 7298.1331133142@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

<mdione(dot)ext(at)orange(dot)com> writes:
> Short and simple: I'm trying to do the following:

> postgres(at)master-db01:~$ psql pnssi_profiles_bench
> psql (9.0.3)
> Type "help" for help.

> pnssi_profiles_bench=# drop SCHEMA _pnssi_slony_bench_profiles_01_110 cascade;
> ERROR: could not find tuple for trigger 37463634

You might try reindexing pg_trigger before doing anything more invasive,
just in case the tuple is there but it's not being found because of a
messed-up index.

> As you can see, this is a slony setup, but I'm not sure that's relevant.

It could be --- Slony plays some not-very-nice games with the system
catalogs, or at least used to. If reindex doesn't fix things I'd
suggest asking about this on the Slony lists.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martin Gregorie 2012-03-07 15:19:51 Re: Fixing the loss of 'template1'
Previous Message Adrian Klaver 2012-03-07 15:10:31 Re: Fixing the loss of 'template1'