From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tim McAuley <mcauleyt(at)tcd(dot)ie>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Date: | 2003-09-26 20:22:08 |
Message-ID: | Pine.LNX.4.44.0309262221340.11938-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-jdbc |
scott.marlowe writes:
> table name too, like Bruce said. The bothersome bit is that in pg_dump,
> it says the line, relative to just this part of the copy command, so you
> don't even know which table is giving the error.
I don't see the problem. Can't you identify the failing command by the
line number that psql gives you?
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-26 20:27:43 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Previous Message | scott.marlowe | 2003-09-26 20:09:21 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-26 20:27:43 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Previous Message | Marc G. Fournier | 2003-09-26 20:12:58 | Re: 2-phase commit |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2003-09-26 20:27:43 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |
Previous Message | scott.marlowe | 2003-09-26 20:09:21 | Re: initdb failure (was Re: [GENERAL] sequence's plpgsql) |