"discourse_solved_solved_topics" 재구축 시 not-null 제약 조건 위반

Steven · 12월 20, 2025, 6:30오후

안녕하세요 여러분!

stable 브랜치의 포럼을 재구축하는 과정에서 solved 플러그인과 관련된 오류가 발생했습니다.

로그는 다음과 같습니다:

2025-12-20 03:48:21.715 UTC [1122] discourse@discourse ERROR:  null value in column "answer_post_id" of relation "discourse_solved_solved_topics" violates not-null constraint
2025-12-20 03:48:21.715 UTC [1122] discourse@discourse DETAIL:  Failing row contains (3735, 35506, null, -1, null, 2021-05-12 18:38:58.11516, 2021-05-12 18:38:58.11516).
2025-12-20 03:48:21.715 UTC [1122] discourse@discourse STATEMENT:  INSERT INTO discourse_solved_solved_topics (
	  topic_id,
	  answer_post_id,
	  topic_timer_id,
	  accepter_user_id,
	  created_at,
	  updated_at
	)
	SELECT
	  tc.topic_id,
	  tc.answer_post_id,
	  tc.topic_timer_id,
	  tc.accepter_user_id,
	  tc.created_at,
	  tc.updated_at
	FROM (
	  SELECT
	    tc.topic_id,
	    CAST(tc.value AS INTEGER) AS answer_post_id,
	    CAST(tc2.value AS INTEGER) AS topic_timer_id,
	    COALESCE(ua.acting_user_id, -1) AS accepter_user_id,
	    tc.created_at,
	    tc.updated_at,
	    ROW_NUMBER() OVER (PARTITION BY tc.topic_id ORDER BY tc.created_at ASC) AS rn_topic,
	    ROW_NUMBER() OVER (PARTITION BY CAST(tc.value AS INTEGER) ORDER BY tc.created_at ASC) AS rn_answer
	  FROM topic_custom_fields tc
	  LEFT JOIN topic_custom_fields tc2 ON tc2.topic_id = tc.topic_id AND tc2.name = 'solved_auto_close_topic_timer_id'
	  LEFT JOIN user_actions ua ON ua.target_topic_id = tc.topic_id AND ua.action_type = 15
	  WHERE tc.name = 'accepted_answer_post_id'
	    AND tc.id > 0
	    AND tc.id <= 0 + 10000
	) tc
	WHERE tc.rn_topic = 1 AND tc.rn_answer = 1
	ON CONFLICT DO NOTHING
	
rake aborted!
StandardError: An error has occurred, all later migrations canceled: (StandardError)

ERROR:  null value in column "answer_post_id" of relation "discourse_solved_solved_topics" violates not-null constraint
DETAIL:  Failing row contains (3735, 35506, null, -1, null, 2021-05-12 18:38:58.11516, 2021-05-12 18:38:58.11516).
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:217:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run'
/var/www/discourse/lib/mini_sql_multisite_connection.rb:109:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:196:in `exec'
/var/www/discourse/plugins/discourse-solved/db/migrate/20250318024953_copy_solved_topic_custom_field_to_discourse_solved_solved_topics.rb:17:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `public_send'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `exec_migration'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `block in exec_migration'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/benchmark-0.4.1/lib/benchmark.rb:305:in `measure'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `exec_migration'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:975:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/benchmark.rb:17:in `realtime'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:974:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:412:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:973:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1187:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1535:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1588:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1534:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `migrate_without_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1606:in `with_advisory_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1261:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1236:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/tasks/database_tasks.rb:270:in `migrate'
/var/www/discourse/lib/tasks/db.rake:267:in `block (2 levels) in <main>'
/var/www/discourse/lib/distributed_mutex.rb:53:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:34:in `synchronize'
/var/www/discourse/lib/tasks/db.rake:242:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.0/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'

Caused by:
PG::NotNullViolation: ERROR:  null value in column "answer_post_id" of relation "discourse_solved_solved_topics" violates not-null constraint (PG::NotNullViolation)
DETAIL:  Failing row contains (3735, 35506, null, -1, null, 2021-05-12 18:38:58.11516, 2021-05-12 18:38:58.11516).
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rack-mini-profiler-4.0.1/lib/patches/db/pg/alias_method.rb:109:in `async_exec'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:217:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `block in run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `block in with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/concurrency/null_lock.rb:9:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:34:in `with_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/active_record_postgres/connection.rb:38:in `run'
/var/www/discourse/lib/mini_sql_multisite_connection.rb:109:in `run'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/mini_sql-1.6.0/lib/mini_sql/postgres/connection.rb:196:in `exec'
/var/www/discourse/plugins/discourse-solved/db/migrate/20250318024953_copy_solved_topic_custom_field_to_discourse_solved_solved_topics.rb:17:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `public_send'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:994:in `exec_migration'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `block in exec_migration'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/benchmark-0.4.1/lib/benchmark.rb:305:in `measure'
/var/www/discourse/lib/freedom_patches/schema_migration_details.rb:8:in `exec_migration'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:975:in `block (2 levels) in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activesupport-8.0.2.1/lib/active_support/benchmark.rb:17:in `realtime'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:974:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:412:in `with_connection'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:973:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1187:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1535:in `block in execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1588:in `ddl_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1534:in `execute_migration_in_transaction'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `each'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1509:in `migrate_without_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `block in migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1606:in `with_advisory_lock'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1454:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1261:in `up'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/migration.rb:1236:in `migrate'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/activerecord-8.0.2.1/lib/active_record/tasks/database_tasks.rb:270:in `migrate'
/var/www/discourse/lib/tasks/db.rake:267:in `block (2 levels) in <main>'
/var/www/discourse/lib/distributed_mutex.rb:53:in `block in synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:49:in `synchronize'
/var/www/discourse/lib/distributed_mutex.rb:34:in `synchronize'
/var/www/discourse/lib/tasks/db.rake:242:in `block in <main>'
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/rake-13.3.0/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
I, [2025-12-20T03:48:21.794538 #1]  INFO -- : gem install geocoder -v 1.8.3 -i /var/www/discourse/plugins/discourse-locations/gems/3.3.8 --no-document --ignore-dependencies --no-user-install
Successfully installed geocoder-1.8.3
1 gem installed
== 20250318024953 CopySolvedTopicCustomFieldToDiscourseSolvedSolvedTopics: migrating 

I, [2025-12-20T03:48:21.795736 #1]  INFO -- : Terminating async processes
I, [2025-12-20T03:48:21.795838 #1]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/15/bin/postmaster -D /etc/postgresql/15/main pid: 45
I, [2025-12-20T03:48:21.795934 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 112
112:signal-handler (1766202501) Received SIGTERM scheduling shutdown...
2025-12-20 03:48:21.796 UTC [45] LOG:  received fast shutdown request
2025-12-20 03:48:21.800 UTC [45] LOG:  aborting any active transactions
2025-12-20 03:48:21.808 UTC [45] LOG:  background worker "logical replication launcher" (PID 59) exited with exit code 1
2025-12-20 03:48:21.809 UTC [54] LOG:  shutting down
2025-12-20 03:48:21.811 UTC [54] LOG:  checkpoint starting: shutdown immediate
2025-12-20 03:48:21.861 UTC [54] LOG:  checkpoint complete: wrote 18 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.039 s, sync=0.006 s, total=0.052 s; sync files=10, longest=0.003 s, average=0.001 s; distance=161 kB, estimate=161 kB
112:M 20 Dec 2025 03:48:21.892 # User requested shutdown...
112:M 20 Dec 2025 03:48:21.892 * Saving the final RDB snapshot before exiting.
2025-12-20 03:48:21.918 UTC [45] LOG:  database system is shut down
112:M 20 Dec 2025 03:48:22.621 * DB saved on disk
112:M 20 Dec 2025 03:48:22.621 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 1016 exit 1>
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.3.0/lib/pups/exec_command.rb:131:in `spawn'
exec failed with the params {"cd"=>"$home", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migrate'"]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.

app.yml에서 solved 플러그인을 삭제하고(- rm -rf discourse-solved 명령 사용) 재구축하는 데 성공했습니다. 포럼 소유자는 이 플러그인이 없어도 큰 문제가 없을 것 같지만, 그래도 이 문제를 해결하고 싶습니다.

문제가 플러그인에서 비롯된 것 같지는 않고, 포럼에서 잘못된 조작이 있었을 가능성이 있습니다. 하지만 데이터베이스를 탐색해 보니 value 컬럼에 최소 20~30개의 \N 항목이 있습니다.

다음은 일부 내용입니다:

id	topic_id	name	value	created at	updated at
1579	35497	accepted_answer_post_id	301435	2021-05-10 20:18:57.780444	2021-05-10 20:18:57.780444
1583	35506	accepted_answer_post_id	\N	2021-05-12 18:38:58.11516	2021-05-12 18:38:58.11516
423	21211	accepted_answer_post_id	153039	2019-09-04 21:01:37.811417	2019-09-04 21:01:37.811417
424	21685	accepted_answer_post_id	156850	2019-09-09 04:39:28.388591	2019-09-09 04:39:28.388591
425	21711	accepted_answer_post_id	157323	2019-09-11 11:51:14.375185	2019-09-11 11:51:14.375185
428	20982	accepted_answer_post_id	157807	2019-09-14 08:53:16.079032	2019-09-14 08:53:16.079032
429	4949	accepted_answer_post_id	157515	2019-09-16 07:57:00.862694	2019-09-16 07:57:00.862694
430	15439	accepted_answer_post_id	158645	2019-09-19 00:56:20.112603	2019-09-19 00:56:20.112603
1603	35710	accepted_answer_post_id	\N	2021-05-19 20:58:06.598697	2021-05-19 20:58:06.598697
701	25377	accepted_answer_post_id	195459	2020-03-26 20:42:14.168898	2020-03-26 20:42:14.168898
434	21868	accepted_answer_post_id	159024	2019-09-22 10:09:09.671605	2019-09-22 10:09:09.671605

솔직히 SQL 쿼리, 특히 터미널을 통한 쿼리 작성에는 서툽니다. 터미널에서 직접 이 행들을 삭제하는 것은 위험하다고 느껴서 자신감이 없습니다.

그래도 이 문제를 해결하기 위해 어떤 방법을 추천해 주실 수 있을까요? 쿼리(어떤 종류의 쿼리?)를 사용해야 할까요? 스크립트를 실행해야 할까요? 아니면 포럼 내에서 직접 처리할 수 있는 방법이 있을까요?

pfaffman · 12월 20, 2025, 7:57오후

다만, 이 플러그인은 코어(core)로 이동되었습니다.

post_id가 Newline인 레코드들이 문제입니다. 데이터베이스에서 해당 레코드들을 삭제하시면 됩니다 (Rails를 통해 가능할 수 있습니다). Ask.discourse.com에서 방법을 알려줄 수 있을 것입니다.

JammyDodger · 12월 20, 2025, 8:55오후

가능한 해결책으로… 현재 주제를 삭제하면 자동으로 해결책이 제거되고 discourse_solved_solved_topics의 기록도 삭제된다고 생각합니다. solved 플러그인이 설치되어 있지 않은 상태에서도 이것이 작동할지는 100% 확신할 수 없지만, 확인해 볼 가치가 있지 않을까요?

data explorer에서 쿼리를 실행해 모든 항목을 가져온 후, 하나를 삭제하고 다시 쿼리를 실행하여 사라졌는지 확인하는 것이 작동 가능한지 쉽게 파악하는 방법이 될 수 있습니다.

주제를 복원해도 discourse_solved_solved_topics의 기록은 복원되지 않으므로(잠재적으로 ), 빠른 ‘삭제 후 복원’ 작업으로 이를 정리할 수 있을지도 모릅니다.

pfaffman · 12월 20, 2025, 9:59오후

해당 기능을 담당하는 코드가 플러그인에 포함되어 있기 때문에 작동하지 않을 것이라고 꽤 확신합니다.

또한 데이터베이스가 깨져 있다고도 꽤 확신합니다. 해당 값(value) 열에는 줄바꿈 문자가 포함되면 안 됩니다. 데이터베이스에서 이를 삭제하는 것이 필요합니다. 그렇지 않으면 새 서버로 이동을 시도하고 이 데이터베이스를 복원할 때(핵심 코어에 포함되어 있으므로 solved가 활성화된 상태로) 이 문제를 다시 처음부터 해결해야 할 것입니다.

JammyDodger · 12월 20, 2025, 10:09오후

아, 그럴 줄 알았어요. 청소를 어디에 보관하는지 확신이 없었거든요.

알렉산더도 비슷한 문제를 겪었고, 데이터베이스(DB) 방식으로 해결한 것 같네요: Error upgrading to latest Discourse -- solved - #4 by Alexander_Wright

Steven · 12월 21, 2025, 7:03오전

@pfaffman님과 @JammyDodger님 감사합니다. 데이터베이스를 파고들어 이 문제를 수정해 보겠습니다.

데이터 탐색기를 통해 문제의 행 목록을 확인했는데, 시간이 매우 제한적인 것 같습니다. 해당 시간대에 플러그인에 문제가 있었던 것일까요?

비슷한 문제를 수정하려는 이 커밋을 확인했습니다.

github.com/discourse/discourse-solved

FIX: Multiple topics may have the same post as its solution (#348)

committed 02:21PM - 26 Mar 25 UTC

nattsw

+169 -28

We are seeing some errors when migrating and adding indexes on `answer_post_id`.… ``` #<StandardError:"An error has occurred, all later migrations canceled:\n\nPG::UniqueViolation: ERROR: could not create unique index \"index_discourse_solved_solved_topics_on_answer_post_id\"\nDETAIL: Key (answer_post_id)=(13006) is duplicated.\n"> ``` This PR modifies the earlier migration, and also adds one before the addition of indexes to remove duplicates.

어쨌든 흥미롭네요. 수정을 시도해 보겠습니다. 매우 민감한 부분이므로 서두르지 않고 시간을 들여 진행하겠습니다.

pfaffman · 12월 21, 2025, 11:49오전

Ask.discourse.com에서 삭제하려는 항목을 모두 찾을 수 있는 쿼리를 얻는 것은 꽤 쉬울 것입니다. 그리고 쿼리의 해당 부분이 올바르게 작동하는 것을 확인한 후, 모든 항목을 삭제할 수 있습니다.

JammyDodger · 12월 21, 2025, 12:56오후

해결 처리를 한 사람이 시스템 사용자인 것도 좀 unusual합니다. Alexander의 에러를 보면, 그에게도 같은 상황이었던 것 같습니다.

비슷한 보고가 두 건이나 있으니, @pfaffman, 마이그레이션에서 엣지 케이스가 누락된 경우일 수 있다고 생각하시나요?

pfaffman · 12월 21, 2025, 1:56오후

짐작은 하지 않겠습니다.

JammyDodger · 12월 21, 2025, 2:19오후

8개월 동안 2건이면 엄밀히 말해 범람한다고 할 수는 없으니, 더 깊이 파고들 만큼은 아닐지도 모릅니다.

다른 보고에도 비슷한 날짜 범위가 있는 것 같습니다:

현재 진행 중인 작업에 대해 크게 유용한 정보는 아니지만, 추가적인 보고가 들어올 경우 도움이 될 수 있습니다.

글		댓글	조회수
Discourse-solved broken migration Self-hosting	4	646	8월 31, 2021
ERROR RecordNotUnique on index_discourse_solved_solved_topics_on_answer_post_id Support solved	7	169	3월 26, 2025
Error upgrading to latest Discourse -- solved Support solved	3	249	4월 19, 2025
Plugin causing errors during rebuild Self-hosting	20	2286	10월 11, 2022
Migration error in 'rename_discourse_rewind_disabled_to_enabled' Self-hosting	25	597	1월 11, 2026

"discourse_solved_solved_topics" 재구축 시 not-null 제약 조건 위반

Related topics