From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Oliver Elphick <olly(at)lfix(dot)co(dot)uk>, PostgreSQL hackers list <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Date: | 2003-09-27 17:00:59 |
Message-ID: | Pine.LNX.4.44.0309271859420.11938-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
Bruce Momjian writes:
> You are assuming it is easy to find what is on a specific line of the
> dump file. I am not sure that is always easy for people with limited
> Unix skills, or MSWin folks. I am not sure I would have thought to add
> the file offset to find the problem COPY line. I guess I would have
> eventually, but it wouldn't have been my first idea, and I might _not_
> have used -f on the load, and if the load took an hour, I would have to
> run it again to get that line number.
That is all besides the point. If adding -f to the command line is for
some reason prohibitive, then the same applies to -e. That is all.
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-27 17:04:52 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Previous Message | Bruce Momjian | 2003-09-27 16:59:03 | Re: Idea for improving speed of pg_restore |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-27 17:04:52 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Previous Message | Bruce Momjian | 2003-09-27 16:34:54 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Prohaska | 2003-09-27 17:01:54 | Re: Tomcat - PostgreSQL - Cannot load JDBC driver class "n |
Previous Message | Bruce Momjian | 2003-09-27 16:53:01 | Re: Statement.cancel() may cancel queries in the future |