Re: another error perhaps to be enhanced

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: another error perhaps to be enhanced
Date: 2013-06-14 18:01:46
Message-ID: CAM3SWZQNwK=Aju4UgrTFcxY=897oCNpjVaHsF8yUFEae35tRww@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2013-06-14 18:03:52 Re: fallocate / posix_fallocate for new WAL file creation (etc...)
Previous Message Joshua D. Drake 2013-06-14 17:54:55 Re: another error perhaps to be enhanced