I tried nice'ing pg_dump without any success in making it bloat memory.
I'm suspicious that there's something Windows-specific in what you're
seeing, because it's fairly hard to credit that nobody's seen this
problem in the ten years or so that libpq has been doing it like that.
Can anyone else
Hm. Can you create a reproducible test case for this?
I think this issue happens when pg_dump is slower than the backend
for some reason.
If so, perhaps injecting a sleep() delay into the right place in pg_dump
or libpq would make it reproducible? I wouldn't have any problem
crediting a test
Shin-ichi MORITA s-mor...@beingcorp.co.jp writes:
If so, perhaps injecting a sleep() delay into the right place in pg_dump
or libpq would make it reproducible?
An alternative way would be running pg_dump with a lower priority.
Actually, I can reproduce this issue by setting the priority of
Hi Tom,
s-mor...@beingcorp.co.jp writes:
I encountered a strange error during pg_dump as below:
pg_dump: Dumping the contents of table t_file_data failed:
PQgetCopyData()
failed.
pg_dump: Error message from server: lost synchronization with server: got
message type d, length 21861
Shin-ichi MORITA s-mor...@beingcorp.co.jp writes:
Hi Tom,
Hm. Can you create a reproducible test case for this?
I think this issue happens when pg_dump is slower than the backend
for some reason.
If so, perhaps injecting a sleep() delay into the right place in pg_dump
or libpq would make it
The following bug has been logged on the website:
Bug reference: 7914
Logged by: Shin-ichi MORITA
Email address: s-mor...@beingcorp.co.jp
PostgreSQL version: 8.4.16
Operating system: Windows Server 2012
Description:
Hi great team,
I encountered a strange error
s-mor...@beingcorp.co.jp writes:
I encountered a strange error during pg_dump as below:
pg_dump: Dumping the contents of table t_file_data failed: PQgetCopyData()
failed.
pg_dump: Error message from server: lost synchronization with server: got
message type d, length 21861
Hm. Can you
