Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) - Mailing list pgsql-hackers

From scott.marlowe
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id Pine.LNX.4.33.0309261449420.1342-100000@css120.ihs.com
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
On Fri, 26 Sep 2003, Peter Eisentraut wrote:

> scott.marlowe writes:
> 
> > but I get basically the same thing if I dump it to a .sql file and do:
> >
> > psql dbname <dbname.sql
> 
> Use psql -f dbname.sql instead.

and the output is:

psql:webport.sql:803: ERROR:  function "odbc_user" already exists with 
same argument types
REVOKE
REVOKE
GRANT
You are now connected as new user "ayousuff".
psql:webport.sql:869: ERROR:  literal newline found in data
HINT:  Use "\n" to represent newline.
CONTEXT:  COPY FROM, line 59
You are now connected as new user "smarlowe".
You are now connected as new user "ayousuff".
CREATE INDEX
CREATE INDEX
CREATE INDEX


the same.  It doesn't tell me which table in my dump caused the problem, 
and it certainly isn't line 59 of the dump file, but of the table 
producing the error.



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: 2-phase commit
Next
From: Tom Lane
Date:
Subject: Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)