When updating today, this migration failed: PG::CardinalityViolation: ERROR: more than one row returned by a subquery used as an expression : INSERT INTO site_settings(name, data_type, value, created_at, updated_at) SELECT 'lounge_welcome_topic_id', 3, id, created_at, updated_at FROM topics WHERE …

Definitely relevant to @gerhard but strongly agree we should have a unique index on name on the site_settings table (and throw away non unique rows in the migration) We will make that happen.

Done in FIX: Make migration resilient against duplicate site settings · discourse/discourse@467c17d · GitHub and FIX: Remove duplicate site settings and add unique index · discourse/discourse@cb70a32 · GitHub

No unique index on site_settings name column

Development

codinghorror (Jeff Atwood) March 20, 2019, 2:48am 2

I think this might be relevant to @gerhard

Topic		Replies	Views
Duplicate key violation in recent upgrade Development	0	264	April 8, 2024
Update failed - PG::UniqueViolation: ERROR Self-hosting	7	955	December 21, 2018
Upgrade fails while migrating Self-hosting	4	969	July 11, 2019
2.7.0.beta2 upgrade failed with ERROR: duplicate key Self-hosting	24	2566	January 26, 2021
Cannot restore database: sql key is duplicated Self-hosting	2	655	August 30, 2022

No unique index on site_settings name column

Related topics