You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Edit: Looks like a Windows-related problem with carriage returns extracting from the archive. However, I'm also getting an error using gunzip on Linux. Any ideas?
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 18729; 0 23208 TABLE DATA seq0062_moe census
pg_restore: [archiver (db)] COPY failed for table "seq0062_moe": ERROR: literal carriage return found in data
HINT: Use "\r" to represent carriage return.
CONTEXT: COPY seq0062_moe, line 501496
WARNING: errors ignored on restore: 1
I'm getting these errors when restoring from the ACS Postgres dump.
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 18620; 0 22495 TABLE DATA seq0008 census
pg_restore: [archiver (db)] COPY failed for table \"seq0008\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0008, line 278389
pg_restore: [archiver (db)] Error from TOC entry 18631; 0 22571 TABLE DATA seq0013_moe census
pg_restore: [archiver (db)] COPY failed for table \"seq0013_moe\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0013_moe, line 400612
pg_restore: [archiver (db)] Error from TOC entry 18648; 0 22695 TABLE DATA seq0022 census
pg_restore: [archiver (db)] COPY failed for table \"seq0022\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0022, line 203989
pg_restore: [archiver (db)] Error from TOC entry 18654; 0 22731 TABLE DATA seq0025 census
pg_restore: [archiver (db)] COPY failed for table \"seq0025\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0025, line 310680
pg_restore: [archiver (db)] Error from TOC entry 18668; 0 22819 TABLE DATA seq0032 census
pg_restore: [archiver (db)] COPY failed for table \"seq0032\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0032, line 446598
pg_restore: [archiver (db)] Error from TOC entry 18707; 0 23077 TABLE DATA seq0051_moe census
pg_restore: [archiver (db)] COPY failed for table \"seq0051_moe\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0051_moe, line 343249
pg_restore: [archiver (db)] Error from TOC entry 18715; 0 23132 TABLE DATA seq0055_moe census
pg_restore: [archiver (db)] COPY failed for table \"seq0055_moe\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0055_moe, line 206873
pg_restore: [archiver (db)] Error from TOC entry 18734; 0 23239 TABLE DATA seq0065 census
pg_restore: [archiver (db)] COPY failed for table \"seq0065\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0065, line 43842
pg_restore: [archiver (db)] Error from TOC entry 18737; 0 23254 TABLE DATA seq0066_moe census
pg_restore: [archiver (db)] COPY failed for table \"seq0066_moe\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0066_moe, line 240366
pg_restore: [archiver (db)] Error from TOC entry 18832; 0 23885 TABLE DATA seq0114 census
pg_restore: [archiver (db)] COPY failed for table \"seq0114\": ERROR: literal carriage return found in data
HINT: Use \"\\r\" to represent carriage return.
CONTEXT: COPY seq0114, line 47232
WARNING: errors ignored on restore: 10
The text was updated successfully, but these errors were encountered:
Edit: Looks like a Windows-related problem with carriage returns extracting from the archive. However, I'm also getting an error using gunzip on Linux. Any ideas?
I'm getting these errors when restoring from the ACS Postgres dump.
The text was updated successfully, but these errors were encountered: