Re: another error perhaps to be enhanced - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: another error perhaps to be enhanced
Date
Msg-id CAM3SWZQNwK=Aju4UgrTFcxY=897oCNpjVaHsF8yUFEae35tRww@mail.gmail.com
Whole thread Raw
In response to Re: another error perhaps to be enhanced  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: another error perhaps to be enhanced  ("Joshua D. Drake" <jd@commandprompt.com>)
List pgsql-hackers
On Fri, Jun 14, 2013 at 10:54 AM, Joshua D. Drake <jd@commandprompt.com> wrote:
> Now, with the error previously shown, which one_idx needs to be reindexed?

Well, you didn't show an actual error message. 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


-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: another error perhaps to be enhanced
Next
From: Jeff Davis
Date:
Subject: Re: fallocate / posix_fallocate for new WAL file creation (etc...)