Stephen Frost [EMAIL PROTECTED] writes:
It seems like pg_restore really should be able to handle COPY errors
correctly by skipping to the end of the COPY data segment when the
initial COPY command comes back as an error.
Send a patch ;-)
regards, tom lane
Magnus's case seemed like a beast of a different animal to me, given it
was a direct index scan using a wildcard based search on a primary key
column; I'd agree I don't know exactly how it would determine a value
different that 1.
But in my example, this misestimation comes between columns that
Wojciech Sobczuk [EMAIL PROTECTED] writes:
I have a 16GB database which is very busy (100 requests per second). After
running for some time (sometimes 2 days sometimes longer sometimes shorter)
postgres hangs. Last time it happened I got the following error in the
log:
ERROR: could
