Re: Seg fault in pg_dump?

No, it isn't a debug-enabled build, and I don't think the debug symbols
package is installed on that system. I've never used GDB, I'm more of an
'applications' programmer, I may need a 'crash' course on it, if you pardon
the pun. However, if it's anything like the debugging tools I used to use
when programming in assembler, aeons ago, just relinking the program with
debug symbols in it could fix the problem. :sigh:

This is on my new production system, I'm getting ready to migrate a backup
system over to 8.2.3, I may be able to do some additional testing there,
assuming I get the same failure.

It doesn't appear that dumpall has the same problem, or at least it didn't
abort when I dumped the entire cluster last night. It doesn't fail when I
dump that entire database either, just when I dump some of the sequences.

What else can I do to help track this down?
--
Mike Nolan

On 4/5/07, Alvaro Herrera < alvherre(at)commandprompt(dot)com> wrote:
>
> Michael Nolan escribió:
> > GDB produces:
> >
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x0804fd6f in dumpSequence ()
>
> Not very helpful -- what does it say if you ask for "bt"? I'm thinking
> this is not a debug-enabled build though. I think you have to install a
> separate RPM package in Fedora to get the debug symbols.
>
> --
> Alvaro Herrera
> http://www.CommandPrompt.com/
> PostgreSQL Replication, Consulting, Custom Development, 24x7 support
>