pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Phillip Smith <phillip.smith@weatherbeeta.com.au>
Cc: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Restoring pg_dump Backup with psql Fails
Date: Fri, 28 Dec 2007 20:54:10 -0800
Message-ID: <4775D2F2.4080502@commandprompt.com> (raw)
In-Reply-To: <004b01c849cd$badabd80$9b0014ac@wbaus090>
References: <004b01c849cd$badabd80$9b0014ac@wbaus090>

Phillip Smith wrote:
> Sorry Tom - I should know better :)
> 
> I've attached the first 512 lines of the output from psql. The whole output
> is 3mb.
> 

You have several problems in this dump. One it appears that some of the 
releations already exist. Did you by chance accidently create stuff 
within template1 at some point?

Secondly you need to look into iconv to fix your invalid UTF8 data.

Joshua D. Drake

> Cheers,
> ~p
> 
>> -----Original Message-----
>> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
>> Sent: Saturday, 29 December 2007 13:26
>> To: Phillip Smith
>> Cc: pgsql-admin@postgresql.org
>> Subject: Re: [ADMIN] Restoring pg_dump Backup with psql Fails
>>
>> "Phillip Smith" <phillip.smith@weatherbeeta.com.au> writes:
>>> But I get a whole bunch of errors, for example:
>>> <snip>
>>> ERROR:  syntax error at or near "all"
>>> LINE 1: all orders over $400.00 - freight free Order 10 of any produ...
>>>         ^
>> Please show us the *first* few errors, not some randomly chosen ones.
>> The above looks like a COPY has failed and psql has started thinking
>> that copy-data lines are commands, but how or why that happened is
>> not in evidence.
>>
>> 			regards, tom lane
> 
> 
> THINK BEFORE YOU PRINT - Save paper if you don't really need to print this
> 
> *******************Confidentiality and Privilege Notice*******************
> 
> The material contained in this message is privileged and confidential to
> the addressee.  If you are not the addressee indicated in this message or
> responsible for delivery of the message to such person, you may not copy
> or deliver this message to anyone, and you should destroy it and kindly
> notify the sender by reply email.
> 
> Information in this message that does not relate to the official business
> of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
> Weatherbeeta, its employees, contractors or associates shall not be liable
> for direct, indirect or consequential loss arising from transmission of this
> message or any attachments
> e-mail.
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 3: Have you checked our extensive FAQ?
> 
>                http://www.postgresql.org/docs/faq




view thread (8+ messages)  latest in thread

Message-ID: <4775D2F2.4080502@commandprompt.com>
Permalink:  ../4775D2F2.4080502@commandprompt.com/
Also on:    postgresql.org/message-id/4775D2F2.4080502@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jd@commandprompt.com, phillip.smith@weatherbeeta.com.au, tgl@sss.pgh.pa.us
  Subject: Re: Restoring pg_dump Backup with psql Fails
  In-Reply-To: <4775D2F2.4080502@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox