Обсуждение: another error perhaps to be enhanced
ERROR: index "foo_idx" We should probably add the schema. 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
On Jun 14, 2013, at 13:38, "Joshua D. Drake" <jd@commandprompt.com> wrote: > > ERROR: index "foo_idx" > > We should probably add the schema. I've noticed similar issues with functions. I'd like to see those schema-qualified as well. > > 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 > > > -- > Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-hackers
I think you'll need to better describe what you mean here. -- Peter Geoghegan
On 06/14/2013 10:47 AM, Peter Geoghegan wrote: > > I think you'll need to better describe what you mean here. > postgres=# create schema foo; CREATE SCHEMA postgres=# create schema bar; CREATE SCHEMA postgres=# create table foo.foo(id serial); NOTICE: CREATE TABLE will create implicit sequence "foo_id_seq" for serial column "foo.id" CREATE TABLE postgres=# create table bar.bar(id serial); NOTICE: CREATE TABLE will create implicit sequence "bar_id_seq" for serial column "bar.id" CREATE TABLE postgres=# create index one_idx on foo.foo(id); CREATE INDEX postgres=# create index one_idx on bar.bar(id); CREATE INDEX postgres=# Now, with the error previously shown, which one_idx needs to be reindexed? 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
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
On 06/14/2013 11:01 AM, Peter Geoghegan wrote: > > 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. 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