On Fri, Jun 10, 2005 at 12:34:15PM -0400, Tom Lane wrote: > "Colin E. Freas" <cef6@xxxxxxxxxxxxxx> writes: > > 2005-06-07 16:02:38 EDTLOG: statement: update pg_class set > > reltriggers=foo.c from (select relname,count(tgrelid) as c from > > pg_class,pg_trigger where pg_class.oid=tgrelid and relnamespace=2200 > > group by relname) foo; > > I'm afraid that database is toast :-(. You managed to overwrite > reltriggers in every row of pg_class, including all the system > catalogs, including some that absolutely positively cannot have > triggers ... like pg_trigger for instance. > > -> try to open pg_class > ... hmm, it says it has triggers > -> try to open pg_trigger to read triggers > ... hmm, it says it has triggers > -> try to open pg_trigger to read triggers > ... hmm, it says it has triggers > -> try to open pg_trigger to read triggers > > ... recurse until out of stack space. IIRC Joe Conway had this problem some time ago, and he managed to get out of it. I don't recall details, maybe searching the archives ... -- Alvaro Herrera (<alvherre[a]surnet.cl>) "El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
