Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 1DCE41E34FD7 for ; Wed, 23 Nov 2011 13:05:18 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RTGG5-0004VV-90 for pgsql-admin@postgresql.org; Wed, 23 Nov 2011 17:05:17 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pANH54nb028133; Wed, 23 Nov 2011 12:05:04 -0500 (EST) To: David Schnur cc: pgsql-admin@postgresql.org Subject: Re: Repeatable crash in pg_dump (with -d2 info) In-reply-to: References: Comments: In-reply-to David Schnur message dated "Wed, 23 Nov 2011 11:03:28 -0500" Date: Wed, 23 Nov 2011 12:05:03 -0500 Message-ID: <28131.1322067903@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 201111/124 X-Sequence-Number: 38718 David Schnur 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