BUG #7865: Unexpected error code on insert of duplicate to composite primary key

From: matti(dot)aarnio(at)methics(dot)fi
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7865: Unexpected error code on insert of duplicate to composite primary key
Date: 2013-02-09 20:25:39
Message-ID: E1U4GzT-0005Q0-9a@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 7865
Logged by: Matti Aarnio
Email address: matti(dot)aarnio(at)methics(dot)fi
PostgreSQL version: 9.2.2
Operating system: Fedora Linux 17/18
Description:

A table:

CREATE TABLE example (
a TIMESTAMP NOT NULL,
b VARCHAR(256) NOT NULL,
c VARCHAR(256) NOT NULL,
PRIMARY KEY(a,b,c)
);

Inserting a duplicate record on this is returning an SQL Error, but the
status code is 0 instead of expected 23505.

This used to work fine in 8.x series, but is now causing trouble in 9.1.7,
and 9.2.3.

My application filters by the status code to detect if the issue is really
duplicate value, or some database service error.

In a few cases we want to see "it is duplicate!" in order to allow an
operation elsewhere.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message tim.romano 2013-02-10 12:27:22 BUG #7866: even after T's child-tables are deleted it cannot have select-rule
Previous Message viswam mamilla 2013-02-09 11:25:48