-
Title
duplicate key value violates unique constraint topology_object_to_object_name_hash_key- Error seen in PostgreSQL logs. -
Description
Below errors are seen in PostgreSQL log.
ERROR: duplicate key value violates unique constraint "topology_object_to_object_name_hash_key"DETAIL: Key (to_object_name_hash)=(6dd9d5f1f8ed7ce01de5a6382e863dbf) already exists.STATEMENT: INSERT INTO topology_object ( to_type, to_unique_id, to_object_name, to_object_name_hash, to_last_updated, to_activity_day_number, to_activity_current_day) VALUES($1, $2, $3, $4, $5, $6, $7) RETURNING * -
Cause
These errors are seen if the log_min_messages parameter in postgresql.conf is to WARN. -
Resolution
log_min_messages parameter should be set to LOG in the file postgresql.conf which is located in the path $FoglightHome\state\postgresql-data.
Additional Information:
These messages can be ignored if log_min_messages parameter is commented out or its value is not set to LOG.
The server takes an optimistic approach when creating a topology object and assumes that it hadn't been created previously. If it had already been created then this error will appear in the logs. This would be the case if a topology object was deleted and then later recreated, and the server will handle the error and restore the original object. This approach tends to be more efficient than running additional queries to check for expired objects whenever attempting to create an object.