From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: pg_dump 'die_on_errors' |
Date: | 2004-08-15 15:32:49 |
Message-ID: | 26417.1092583969@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> Attached patch sets client_min_messages as above and gives some
> context to errors messages, eg:
> pg_restore: [archiver (db)] Error from TOC Entry 19; 1255 16438403 FUNCTION foo() pjw
> pg_restore: [archiver (db)] could not execute query: ERROR: no schema has been selected to create in
It'd be substantially *more* helpful if it reported the failing command.
(The TOC entry label is not of interest to anyone except pg_dump hackers
such as yourself.) I went around a release or so back and made sure
that pg_dump would always give the text of a failed query, but I forgot
to consider pg_restore :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-15 15:40:18 | Re: [Fwd: Re: [pgsql-hackers-win32] Import from Linux to |
Previous Message | Bruce Momjian | 2004-08-15 13:48:24 | Re: 8.0 beta status |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-15 15:40:18 | Re: [Fwd: Re: [pgsql-hackers-win32] Import from Linux to |
Previous Message | Gavin Sherry | 2004-08-15 10:59:08 | ALTER SCHEMA ... SET TABLESPACE |