From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
---|---|
To: | Holec <holec(at)email(dot)cz> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6233: pg_dump hangs with Access Violation C0000005 |
Date: | 2011-09-29 07:48:00 |
Message-ID: | 4E8422B0.5060404@ringerc.id.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)email(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | depstein | 2011-09-29 10:06:06 | Re: Problems with ENUM type manipulation in 9.1 |
Previous Message | Craig Ringer | 2011-09-29 07:44:37 | Re: BUG #5800: "corrupted" error messages (encoding problem ?) |