From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Show schema in COPY error CONTEXT strings |
Date: | 2010-05-03 17:46:05 |
Message-ID: | 19275.1272908765@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, May 3, 2010 at 1:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> My own preference for what to do about this is to leave the primary
>> message texts alone and add additional error-message fields for object
>> name and schema. This would address the need without making messages
>> uglier for the large fraction of users who don't really care; and it
>> would also help us get closer to the SQL standard's expectations for
>> error reporting.
> This might help people who use tools to parse the output, but I'm not
> sure that's who is having this problem.
If you're using psql, "\set VERBOSITY verbose" would presumably show you
the extra fields, or we could invent a new setting that adds just these
fields. Likewise you can get it in the server log if you need it. I'm
not a fan of cramming more stuff into primary message texts on the
theory that that's the only useful field.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stefan Kaltenbrunner | 2010-05-03 18:04:50 | Streaming replication - unable to stop the standby |
Previous Message | Robert Haas | 2010-05-03 17:34:32 | Re: Show schema in COPY error CONTEXT strings |