Robert Haas writes:
> On Mon, Aug 27, 2012 at 9:58 AM, Bruce Momjian wrote:
>> 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
On Mon, Aug 27, 2012 at 9:58 AM, Bruce Momjian wrote:
> 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;
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 res
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://postgresq
David Schnur writes:
> I probably can't get a stack trace, but I was able to reproduce it with
> just that function. Without the function, pg_dump works fine. I can DROP
> the function, pg_dump works, then add it back again and pg_dump crashes.
Hmph. I still can't reproduce this here, which se
