| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL hackers list <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
| Date: | 2003-09-27 10:08:20 |
| Message-ID: | Pine.LNX.4.44.0309271207180.11938-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
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(at)gmx(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sven Schwyn | 2003-09-27 10:51:50 | Modification Dates |
| Previous Message | Peter Eisentraut | 2003-09-27 09:31:04 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc G. Fournier | 2003-09-27 12:13:27 | Re: 2-phase commit |
| Previous Message | Kevin Brown | 2003-09-27 10:00:21 | Re: invalid tid errors in latest 7.3.4 stable. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-09-27 16:29:47 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
| Previous Message | Peter Eisentraut | 2003-09-27 09:31:04 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |