"Mason Hale" <masonhale@xxxxxxxxx> writes: > Then I noticed was that our original dump file from 1 week ago was 7GB, and > the one today was 14GB. > We've had a lot of db activity, but I doubt our database has doubled in size > in just one week. > Now I'm thinking that the 7GB dump file was somehow truncated or aborted > before it was finished. (I ran the pg_dump as a background job, and didn't > capture the output... so there may have been an error I didn't see). > Does this file truncation theory sound consistent with the symptoms I > reported? Or does the 'single corrupted row of data' theory ring truer? Hmm ... truncation would explain the weird pg_restore error, I think, but not the problem where it seemed to be misinterpreting the first row of COPY data. regards, tom lane
