Обсуждение: error during pg_dump
I got this error while doing a pg_dump on one of my tables -- any ideas? pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: SQL command to dump the contents of table "users" failed: PQendcopy() failed. pg_dump: Error message from server: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: The command was: COPY public.users (id, "password", email, firstname, lastname, dob, gender, timecreated, lastmodified, pageviews, status, address, city, zip, country, state, phone, lovestatus, interests, highschool, college, company, description, matchdescription, hideage, hideprofile, hidepicture, hidejournal, lastlogin, newsletter, offer, specialoffer, listpage, listpage2, permissions, randomid, nextpage, whosinviewed, yahooviewed, hotmailviewed, outlookviewed, loginid, numcontacts, inviteid, inviterid, numlogins, lastoffertime, hidelocation, hidestatus, emailpref) TO stdout; Thanks, Akash
I got this error while doing a pg_dump on one of my tables -- any ideas? pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: SQL command to dump the contents of table "users" failed: PQendcopy() failed. pg_dump: Error message from server: ERROR: invalid memory alloc request size 18446744073709551613 pg_dump: The command was: COPY public.users (id, "password", email, firstname, lastname, dob, gender, timecreated, lastmodified, pageviews, status, address, city, zip, country, state, phone, lovestatus, interests, highschool, college, company, description, matchdescription, hideage, hideprofile, hidepicture, hidejournal, lastlogin, newsletter, offer, specialoffer, listpage, listpage2, permissions, randomid, nextpage, whosinviewed, yahooviewed, hotmailviewed, outlookviewed, loginid, numcontacts, inviteid, inviterid, numlogins, lastoffertime, hidelocation, hidestatus, emailpref) TO stdout; Thanks, Akash
Akash Garg <akash.garg@gmail.com> writes: > I got this error while doing a pg_dump on one of my tables -- any ideas? > pg_dump: ERROR: invalid memory alloc request size 18446744073709551613 Did you really transcribe that accurately? The number's an order of magnitude too large to fit in even an int64, and it's quite hard to see how a value wider than int32 could arrive at palloc anyway. In any case, I suppose this is a corrupted-data issue; you need to find and delete the corrupted row (or rows). There are past discussions in the archives that might help. regards, tom lane