From: Bruce Momjian <bruce@momjian.us>
To: David Schnur <dnschnur@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: [ADMIN] Repeatable crash in pg_dump (with -d2 info)
Date: Mon, 27 Aug 2012 09:58:52 -0400
Message-ID: <20120827135852.GG11088@momjian.us> (raw)
In-Reply-To: <CAANiQEkmH19QOL5TYd1j2+qjUWERyMf9engUDDwB7GNo8aNLHw@mail.gmail.com>
References: <CAANiQEm92w70rapQhitV1qL0tpkNRo5qjpwo2fdg+iZ-AURMCg@mail.gmail.com>
<28131.1322067903@sss.pgh.pa.us>
<CAANiQE=fjCFLp2DvUM9r3GVA4+khuyaQ9UFaee7HzFzEkJuYvw@mail.gmail.com>
<346.1322071656@sss.pgh.pa.us>
<CAANiQEndAdY+_tF_Pb7njmuQAQUsN+_gBYPOi6TtLNGPEBGUZg@mail.gmail.com>
<29791.1322528434@sss.pgh.pa.us>
<CAANiQEkmH19QOL5TYd1j2+qjUWERyMf9engUDDwB7GNo8aNLHw@mail.gmail.com>
On Tue, Jan 17, 2012 at 04:46:50PM -0500, David Schnur wrote:
> I finally had time to test this further on a variety of systems, and was unable
> to reproduce on any non-Windows platform. The dump even works fine on Windows
> XP; just not Windows 7.
>
> This prompted me to do a little more research, and this time I found this
> thread from Sept. 2011:
>
> http://postgresql.1045698.n5.nabble.com/
> BUG-6233-pg-dump-hangs-with-Access-Violation-C0000005-td4851598.html
>
> From Tom Lane in the above thread:
>
>
> Hmm. I can see how that would happen if you're using one of the Windows
> environments wherein malloc's done inside libpq have to be free'd inside
> libpq. (The PQExpBuffer support code is in libpq...)
>
>
>
> However, the flaw in that explanation is that it would basically mean
> pg_dump doesn't work at all on Windows, at least not if you have any
> user-defined functions, and probably some other cases too because there
> seem to be multiple instances of the dubious coding. It's a bit hard to
> believe that nobody's noticed that before.
>
>
> This appears to describe exactly the issue I'm encountering, and my build is in
> fact linked against the static runtime. I guess the reason this hasn't come up
> sooner is because most Windows users either use the 'official' binaries rather
> than compiling from source, or link against the dynamic runtime.
>
> Is this something I could expect to be fixed in the near future, or is it
> enough of an edge case that I should come up with some solution or work-around
> on my own? Thanks,
Late reply, but I don't see any way we could fix this easily.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
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: bruce@momjian.us, dnschnur@gmail.com, tgl@sss.pgh.pa.us, pgsql-bugs@postgresql.org
Subject: Re: [ADMIN] Repeatable crash in pg_dump (with -d2 info)
In-Reply-To: <20120827135852.GG11088@momjian.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