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

From Peter Eisentraut
Subject Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
Date
Msg-id Pine.LNX.4.44.0309271207180.11938-100000@peter.localdomain
Whole thread Raw
In response to Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)  (Oliver Elphick <olly@lfix.co.uk>)
Responses Re: initdb failure (was Re: [GENERAL] sequence's plpgsql)
List pgsql-hackers
Oliver Elphick writes:

> +    <para>
> +     With a large dump, it may be difficult to identify where any errors are
> +     occurring.  You may use the -e option to psql to print the SQL commands
> +     as they are run, so that it is easy to see precisely which commands are
> +     causing errors.
>      </para>

That is just not true.  If you use -f, it will tell you the line number of
the command causing the error.  Add the line number of the COPY error
message, there you have it.

-- 
Peter Eisentraut   peter_e@gmx.net



pgsql-hackers by date:

Previous
From: Kevin Brown
Date:
Subject: Re: invalid tid errors in latest 7.3.4 stable.
Next
From: "Marc G. Fournier"
Date:
Subject: Re: 2-phase commit