| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Gordon Ross" <G(dot)Ross(at)ccw(dot)gov(dot)uk> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Problems dumping database from 7.3.1 |
| Date: | 2004-05-12 16:51:10 |
| Message-ID: | 26187.1084380670@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Gordon Ross" <G(dot)Ross(at)ccw(dot)gov(dot)uk> writes:
>> 4. Do whatever it takes in the psql session to provoke crash
>> and send along the output of bt.
> Program received signal SIGSEGV, Segmentation fault.
> 0x806ba0a in nocachegetattr () at eval.c:88
> 88 eval.c: No such file or directory.
> (gdb) bt
> #0 0x806ba0a in nocachegetattr () at eval.c:88
> #1 0x80d41ec in ExecEvalVar () at eval.c:88
> #2 0x80d549c in ExecEvalExpr () at eval.c:88
> #3 0x80d5809 in ExecTargetList () at eval.c:88
Hmm. The file/line references are obviously wrong, but let's assume
that the function names are right (they at least look plausible).
What exactly was the query that provoked this?
Also, could we see \d output for the table(s) involved?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jared Evans | 2004-05-12 17:12:47 | How to determine if ODBC was compiled in? |
| Previous Message | Gordon Ross | 2004-05-12 14:14:55 | Re: Problems dumping database from 7.3.1 |