From: Tom Lane <tgl@sss.pgh.pa.us>
To: David Schnur <dnschnur@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Repeatable crash in pg_dump (with -d2 info)
Date: Wed, 23 Nov 2011 12:05:03 -0500
Message-ID: <28131.1322067903@sss.pgh.pa.us> (raw)
In-Reply-To: <CAANiQEm92w70rapQhitV1qL0tpkNRo5qjpwo2fdg+iZ-AURMCg@mail.gmail.com>
References: <CAANiQEm92w70rapQhitV1qL0tpkNRo5qjpwo2fdg+iZ-AURMCg@mail.gmail.com>
David Schnur <dnschnur@gmail.com> writes:
> I'm seeing pg_dump [8.3.15 Windows] crash reproducibly against a particular
> database.
Can you provide a stack trace from the crash? There's some info about
that here:
http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows
though I think it's oriented towards backend crashes more than client-side
crashes.
Alternatively, do you have the SQL definition for the function you think
is causing the crash? There's not much that anybody else is going to be
able to do about this unless you can provide a reproducible test case.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, dnschnur@gmail.com
Subject: Re: Repeatable crash in pg_dump (with -d2 info)
In-Reply-To: <28131.1322067903@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox