From: | Michael Fuhr <mike(at)fuhr(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Nolan <htfoot(at)gmail(dot)com>, pgsql general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump seg fault on sequences |
Date: | 2007-04-15 01:59:39 |
Message-ID: | 20070415015939.GA76762@winnie.fuhr.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Apr 14, 2007 at 06:26:22PM -0400, Tom Lane wrote:
> "Michael Nolan" <htfoot(at)gmail(dot)com> writes:
> > I've narrowed down the conditions under which pg_dump in 8.2.3 is creating a
> > segmentation fault.
> > It appears to happen only when dumping a sequence that is created for a
> > serial data element.
>
> Thanks for the test case --- I can reproduce this now on 8.2 and HEAD too.
> Will take a look tomorrow if no one beats me to it.
(gdb) bt
#0 0x0001e500 in dumpTable (fout=0x53498, tbinfo=0x8c7e0) at pg_dump.c:8733
#1 0x0001f12c in dumpDumpableObject (fout=0x53498, dobj=0x8c7e0) at pg_dump.c:5009
#2 0x00020dd8 in main (argc=4, argv=0x6e) at pg_dump.c:691
(gdb) l 8733,+1
8733 appendPQExpBuffer(query, ".%s;\n",
8734 fmtId(owning_tab->attnames[tbinfo->owning_col - 1]));
(gdb) p owning_tab->attnames
$1 = (char **) 0x0
--
Michael Fuhr
From | Date | Subject | |
---|---|---|---|
Next Message | Alain Roger | 2007-04-15 07:33:12 | issue when export/import table including pictures |
Previous Message | Guy Rouillier | 2007-04-15 00:35:42 | Re: Evaluate only one CASE WHEN in a select |