Where to get this fix in binary form for Windows 32-bit ?
Here, but you will need to wait until 9.3.5 is out:
http://www.postgresql.org/download/windows/.
When 9.3.5 or Windows x32 nightly build or test build will be out ?
Andrus.
--
Sent via pgsql-general mailing list
I looked back at the previous thread you mentioned (bug #7914) and was
reminded that we never did understand what was going on in that report.
I'm not sure if you are seeing the same thing though. That user reported
that he was able to see pg_dump's memory consumption bloating well beyond
what
Andrus kobrule...@hot.ee writes:
I looked back at the previous thread you mentioned (bug #7914) and was
reminded that we never did understand what was going on in that report.
I'm not sure if you are seeing the same thing though. That user reported
that he was able to see pg_dump's memory
But I wouldn't
call that a reliable fix. You'd be better off applying the patch.
Where to get this fix in binary form for Windows 32-bit ?
pg_dump.exe uses files below [1]. Is it sufficient to replace libpq.dll file
?
Where to get its compiled version or how to compile it in Windows ?
[1]
On Fri, May 9, 2014 at 2:37 AM, Andrus kobrule...@hot.ee wrote:
Where to get this fix in binary form for Windows 32-bit ?
Here, but you will need to wait until 9.3.5 is out:
http://www.postgresql.org/download/windows/.
If you are in a hurry, you can still compile manually pg_dump and
deploy it
After upgrading server to Postgres 9.3 in Debian customer cannot create
backups anymore. pg_dump returns
error lost synchronization with server:
C:\myapp\..\pg_dump\pg_dump.exe -ib -Z3 -f C:\mybackup.backup -Fc -h
1.2.3.4 -U user -p 5432 mydb
pg_dump: Dumping the contents of table attachme
Andrus kobrule...@hot.ee writes:
pg_dump: Dumping the contents of table attachme failed: PQgetCopyData()
failed.
pg_dump: Error message from server: lost synchronization with server: got
message type d, length 5858454
pg_dump: The command was: COPY firma1.attachme (id, idmailbox, attachname,
Hi!
pg_dump: Error message from server: lost synchronization with server: got
message type d, length 5858454
I think this is probably an out-of-memory situation inside pg_dump, ie
libpq failing to make its input buffer large enough for the incoming row.
It's hard to believe that there's not
Andrus Moor wrote
Dump worked for years without issues when server was 32 bit Windows 2003
server and Postgres and pg_dump were earlier version 9 (but after upgrade
new rows are added to attachme table).
How to create backup copies or diagnose the issue ?
I can change pg_dump execution
Hi!
Given this is an upgrade, though the specifics were omitted, is there some
possibility of a pg_dump/server version mis-match being the cause. I could
see where a 32-bit client connecting to a 64bit server could possible
exhibit apparent memory-related issues.
pg_dump is 32-bit version.
Hi!
Given this is an upgrade, though the specifics were omitted, is there some
possibility of a pg_dump/server version mis-match being the cause. I could
see where a 32-bit client connecting to a 64bit server could possible
exhibit apparent memory-related issues.
pg_dump is 32-bit version.
Andrus kobrule...@hot.ee writes:
Given this is an upgrade, though the specifics were omitted, is there some
possibility of a pg_dump/server version mis-match being the cause. I could
see where a 32-bit client connecting to a 64bit server could possible
exhibit apparent memory-related issues.
12 matches
Mail list logo
