Re: BUG #6233: pg_dump hangs with Access Violation C0000005 - Mailing list pgsql-bugs

From Craig Ringer
Subject Re: BUG #6233: pg_dump hangs with Access Violation C0000005
Date
Msg-id 4E8422B0.5060404@ringerc.id.au
Whole thread Raw
In response to BUG #6233: pg_dump hangs with Access Violation C0000005  ("Holec" <holec@email.cz>)
Responses Re: BUG #6233: pg_dump hangs with Access Violation C0000005  ("Pavel Holec" <holec@email.cz>)
Re: BUG #6233: pg_dump hangs with Access Violation C0000005  ("Pavel Holec" <holec@email.cz>)
List pgsql-bugs
On 09/29/2011 05:18 AM, Holec wrote:
>
> The following bug has been logged online:
>
> Bug reference:      6233
> Logged by:          Holec
> Email address:      holec@email.cz
> PostgreSQL version: 8.4.8
> Operating system:   Windows 7
> Description:        pg_dump hangs with Access Violation C0000005
> Details:
>
> I use pg_dump on Windows 7 with:
> pg_dump -i -h 192.168.2.2 -p 5432 -U user -F c -b -v -f file.backup mydb


Does this crash happen when you back up a different database? Say, if
you back up the `template1' database, does it crash then too?

Is this a 32-bit or 64-bit install of Windows 7? If 64-bit, are you
using a 32-bit or 64-bit build of PostgreSQL?

Is there any antivirus software on the machine? If so, what type and
version? Does the problem still happen if you turn it off and re-test?

--
Craig Ringer

pgsql-bugs by date:

Previous
From: Craig Ringer
Date:
Subject: Re: BUG #5800: "corrupted" error messages (encoding problem ?)
Next
From:
Date:
Subject: Re: Problems with ENUM type manipulation in 9.1