duplicate keys in postgresql during lemonldap initial configuration
Hi,
During lemonldap initial configuration, we get these types of messages:
2022-03-07 16:50:04.771 UTC [116] ERROR: duplicate key value violates unique constraint "lmconfig_pkey"
2022-03-07 16:50:04.771 UTC [116] DETAIL: Key (cfgnum)=(1) already exists.
2022-03-07 16:50:04.771 UTC [116] STATEMENT: INSERT INTO lmConfig (data,cfgNum) VALUES ($1,$2)
2022-03-07 16:50:05.245 UTC [118] ERROR: duplicate key value violates unique constraint "lmconfig_pkey"
2022-03-07 16:50:05.245 UTC [118] DETAIL: Key (cfgnum)=(1) already exists.
2022-03-07 16:50:05.245 UTC [118] STATEMENT: INSERT INTO lmConfig (data,cfgNum) VALUES ($1,$2)
2022-03-07 16:50:05.409 UTC [119] ERROR: duplicate key value violates unique constraint "lmconfig_pkey"
2022-03-07 16:50:05.409 UTC [119] DETAIL: Key (cfgnum)=(1) already exists.
2022-03-07 16:50:05.409 UTC [119] STATEMENT: INSERT INTO lmConfig (data,cfgNum) VALUES ($1,$2)
2022-03-07 16:51:41.316 UTC [511] ERROR: duplicate key value violates unique constraint "lmconfig_pkey"
2022-03-07 16:51:41.316 UTC [511] DETAIL: Key (cfgnum)=(193) already exists.
2022-03-07 16:51:41.316 UTC [511] STATEMENT: INSERT INTO lmConfig (data,cfgNum) VALUES ($1,$2)
Maybe the process that store each key is launched in parallel, causing duplicate configuration number?