Re: another error perhaps to be enhanced

On 06/14/2013 11:01 AM, Peter Geoghegan wrote:
>
> On Fri, Jun 14, 2013 at 10:54 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> Now, with the error previously shown, which one_idx needs to be reindexed?
>
> Well, you didn't show an actual error message.

ERROR: index "foo_idx"

Is not an error message? Granted I didn't show the whole error message
but my point is, it should ALWAYS be fully qualified.

> But if you "\set
> VERBOSITY verbose" within psql while connected to a 9.3 server, you'll
> get fully qualified details of the constraint blamed for the error, if
> any. Example:
>
> postgres=# insert into a(a, b) values (3, 'test');
> ERROR: 23505: duplicate key value violates unique constraint "a_pkey"
> DETAIL: Key (a)=(3) already exists.
> SCHEMA NAME: public
> TABLE NAME: a
> CONSTRAINT NAME: a_pkey
> LOCATION: _bt_check_unique, nbtinsert.c:398
>
>

I was looking in the logs.

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats