Re: pg_restore: custom archiver unexpected end of file , ERROR: missing data for column - Mailing list pgsql-general

From Khangelani Gama
Subject Re: pg_restore: custom archiver unexpected end of file , ERROR: missing data for column
Date
Msg-id 4f45b27940caecb8a62d568605e014e2@mail.gmail.com
Whole thread Raw
In response to Re: pg_restore: custom archiver unexpected end of file , ERROR: missing data for column  (Adrian Klaver <adrian.klaver@aklaver.com>)
List pgsql-general
> Adrian you might be right I have just tried to pg_restore on the same
> server(8.4.2), I get the same errors related to xml. Can someone
> advise if the following XML file as an example is in the correct state or
> not:

The other strange thing is:

ERROR: missing data for column "fpp_cde"
CONTEXT: COPY audit, line 2565159: "4585427 21~21~21 5143 0 2013-12-01
15:03:18.336718 <?xml version="1.0" encoding="UTF-8"?>\r\n<nonF..."
STATEMENT: COPY audit (aud_id, grp_cde, act_typ, aud_ver, usr_id,
aud_device_id, aud_ts, aud_xml,

aud_id      4585427
grp_code 21~21~21
act_type 5143
aud_ver  0
usr_id 2013-12-01 15:03:18.336718 ???? Is this not aud_ts?
aud_device_id  <?xml version="1.0" encoding="UTF-8"?>\r\n<nonF... ?????
Is this not aud_xml?

Which begs the question where did usr_id and aud_device_id go?

I  have tried to restore the dump which I created using postgres 9 binaries
from postgres 8 database, I got more data issues. The problem it's the data
inside the database that's broken. Application developers are looking at the
problem. Thanks very much for your help , much appreciated.


--
Adrian Klaver
adrian.klaver@aklaver.com


CONFIDENTIALITY NOTICE
The contents of and attachments to this e-mail are intended for the addressee only, and may contain the confidential
information of Argility (Proprietary) Limited and/or its subsidiaries. Any review, use or dissemination thereof by
anyone
other than the intended addressee is prohibited.If you are not the intended addressee please notify the writer
immediately
and destroy the e-mail. Argility (Proprietary) Limited and its subsidiaries distance themselves from and accept no
liability
for unauthorised use of their e-mail facilities or e-mails sent other than strictly for business purposes.



pgsql-general by date:

Previous
From: Nathaniel Talbott
Date:
Subject: Re: (Relatively) Oversized Checkpoint
Next
From: Kevin Grittner
Date:
Subject: Re: Troubles with Postgresql performance