Re: i have a core file on running gdb the op

"surabhi.ahuja" <surabhi(dot)ahuja(at)iiitb(dot)ac(dot)in> writes:
> (gdb) bt
> #0 0xffffe410 in ?? ()
> #1 0x426c2d17 in ?? ()
> #2 0x0820d40a in yycheck ()
> #3 0x080a56be in cookDefault ()
> #4 0x080a59b1 in RelationTruncateIndexes ()
> #5 0x080a608b in UpdateIndexRelation ()
> #6 0x080a2b97 in recordDependencyOnSingleRelExpr ()
> #7 0x080a28e1 in deleteDependentObjects ()
> #8 0x081747db in check_circularity ()
> #9 0x080a860f in OpclassnameGetOpcid ()
> #10 0x081742e0 in aclupdate ()
> #11 0x08172c5f in ProcessUtility ()
> #12 <signal handler called>
> #13 0xffffe410 in ?? ()
> #14 0x08170afb in ProcessQuery ()
> #15 0x0813e3e5 in replace_outer_var ()
> #16 0x426aee42 in ?? ()

Unfortunately that backtrace is just silly, eg, UpdateIndexRelation
would never call RelationTruncateIndexes, which would never call
cookDefault, etc. You'll probably need to rebuild Postgres with
--enable-debug to get a useful trace.

regards, tom lane