From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | el dorado <do_ra_do(at)mail(dot)ru> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problems with pg_dump for PG8.4 for WinXP (MinGW build) |
Date: | 2009-09-15 08:28:57 |
Message-ID: | 9837222c0909150128i4840d76en9ea72dea7fd60113@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2009/9/15 el dorado <do_ra_do(at)mail(dot)ru>:
> Hello!
> I need PG 8.4 built from source code for WinXP. So I got archive postgresql-8.4.1.tar.gz, unpacked it and built postgres by MinGW, as usual:
> configure --witout-zlib
> make
> make install
>
> Everything seeds to be fine until we tried to test pg_dump. It failed (not always but often).
> Command:
> pg_dump -U postgres -v -f mydump.sql TEST_DB
>
> The end of output:
> pg_dump: reading triggers for table "test_table"
> pg_dump: reading dependency data
> pg_dump: saving encoding = UTF8
> pg_dump: saving standard_conforming_string = off
> pg_dump: saving database definition
>
> And here we get a message 'an unhandled win32 exception occured in pg_dump.exe(1788)'
> (digits in brackets varies for different runs of pg_dump)
>
> There are no such problems for ready biniries.
Given that, it seems to be something with your mingw setup causing it.
I think you'll have to get yourself a backtrace using gdb (the native
debugger tools can usually not get usable backtraces from a a mingw
build).
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | std pik | 2009-09-15 09:41:05 | hardware information |
Previous Message | el dorado | 2009-09-15 08:21:49 | Problems with pg_dump for PG8.4 for WinXP (MinGW build) |