Re: [Roundup-users] Docker Container 2.5.0 / UniqueViolation: duplicate key value violates unique constraint "_issue_pkey"

[Ralf S. <rs...@ru...>]

On Wed, Oct 29, 2025 at 07:31:32AM +0000, SCHLEMMER Norbert wrote:
> Hello All
> 
> Running the Roundup Docker container 2.5.0-1 with PostgreSQL 18 and Debian 13 / Trixie as host
> 
> An export was created from the productive Roundup instance 2.3.0.
> After importing in version 2.5.0, new messages can be added to an
> existing issue but creating a new issue result in this violation; see
> logs attached (the import process takes approximately 6 hours...).

Umm, how much data do you have in that database?
If you're migrating between the same version of roundup *and* the same
database, an SQL dump/restore should be *much* faster.

Note that using the roundup-export / roundup-import is not recommended for
version upgrade, that should happen in-place. This might be the reason
of the error-message you're seeing.

> UniqueViolation: duplicate key value violates unique constraint "_issue_pkey" DETAIL: Key (id)=(3) already exists. 	Python 3.13.5
> /usr/local/bin/python3.13

Hmm, this might be because a retired node (e.g. an issue) is first
created and then retired, it could produce a duplicate primary key if a
non-retired node *with the same key* already exists.

But under normal circumstances duplicate primary keys should not occur
(even including retired nodes).

Kind regards
Ralf
-- 
Dr. Ralf Schlatterbeck                  Tel:   +43/2243/26465-16
Open Source Consulting                  www:   www.runtux.com
Reichergasse 131, A-3411 Weidling       email: of...@ru...