Re: [GENERAL] pgdump error "Could not open file pg_clog/0B8E: No such file or directory"

2013-04-25 Thread jesse . waters
ctually exist in the pg_clog directory? > > >> pg_dump: The command was: COPY blob_store.blobs (blob_id, mime_type, >> binary_data, create_ts) TO stdout; >> >> Command used, pretty standard >> pg_dump -Fc -f >> >> >> TIA, >> >> Jess

[GENERAL] pgdump error "Could not open file pg_clog/0B8E: No such file or directory"

2013-04-24 Thread jesse . waters
access status of transaction 3101708884 DETAIL: Could not open file pg_clog/0B8E: No such file or directory. pg_dump: The command was: COPY blob_store.blobs (blob_id, mime_type, binary_data, create_ts) TO stdout; Command used, pretty standard pg_dump -Fc -f TIA, Jesse Waters -- Sent via

Re: [GENERAL] UTF8 frustrations

2007-09-05 Thread jesse . waters
ing CONTEXT: COPY logs, line 69238382 WARNING: errors ignored on restore: 1 Jesse Waters ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq

[GENERAL] UTF8 frustrations

2007-09-04 Thread jesse . waters
uence does not match the encoding expected by the server, which is controlled by "client_encoding". CONTEXT: COPY logs, line 69238382 UTF8 to UTF8 and everything in between is UTF8, and it still fails, I'm tempted to delete this record and keep going but I'm de