Enabling Primary Key Enforement in v7.2 - disposition of existing data

Hi,

Vertica does check the existing data prior to enabling primary key enforcement. Here is a simple example:

dbadmin=> CREATE TABLE test (col1 INT NOT NULL PRIMARY KEY, col2 INT);
CREATE TABLE
dbadmin=> INSERT INTO test VALUES (1, 1);
 OUTPUT
--------
      1
(1 row)

dbadmin=> INSERT INTO test VALUES (1, 2);
 OUTPUT
--------
      1
(1 row)

dbadmin=> ALTER TABLE test ALTER CONSTRAINT C_PRIMARY ENABLED;
ERROR 6745:  Duplicate key values: 'col1=1' -- violates constraint 'public.test.C_PRIMARY'
dbadmin=> SELECT * FROM primary_keys limit 1;
   constraint_id   | constraint_name | column_name | ordinal_position | table_name | constraint_type | is_enabled | table_schema
-------------------+-----------------+-------------+------------------+------------+-----------------+------------+--------------
 45035996273791192 | C_PRIMARY       | col1        |                1 | test       | p               | f          | public
(1 row)

dbadmin=> DELETE FROM test WHERE col2 = 2;
 OUTPUT
--------
      1
(1 row)

dbadmin=> ALTER TABLE test ALTER CONSTRAINT C_PRIMARY ENABLED;
ALTER TABLE
dbadmin=> SELECT is_enabled FROM primary_keys WHERE constraint_name = 'C_PRIMARY';
 is_enabled
------------
 t
(1 row)

dbadmin=> INSERT INTO test VALUES (1, 2);
ERROR 6745:  Duplicate key values: 'col1=1' -- violates constraint 'public.test.C_PRIMARY'

Thanks!

Great thanks.   Now if we can just get it (or analyze_constraints) to give the option to *remove* duplicates