Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFScu-00D7QC-Gx for pgsql-general@arkaria.postgresql.org; Mon, 25 Nov 2024 06:31:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1tFSct-00CcpH-7m for pgsql-general@arkaria.postgresql.org; Mon, 25 Nov 2024 06:31:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1tFScs-00Cco0-SZ for pgsql-general@lists.postgresql.org; Mon, 25 Nov 2024 06:31:14 +0000 Received: from mail-ed1-x534.google.com ([2a00:1450:4864:20::534]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1tFScm-003eLB-Lv for pgsql-general@postgresql.org; Mon, 25 Nov 2024 06:31:13 +0000 Received: by mail-ed1-x534.google.com with SMTP id 4fb4d7f45d1cf-5ced377447bso5446755a12.1 for ; Sun, 24 Nov 2024 22:31:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732516267; x=1733121067; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=yskXsG/Gi9+av4YhT+CVLjJSCJpXUpqc1RCEEwAf/7k=; b=jGJGj0oFHERteXZ+uSJOnVoTJhIVjgI1soMoNOus+stTJ/XEv7t74BEFzBnJHiZkHc DRA15afSkDiIN/1tHehuh/+g+HnISjsUMC2f31/mXr1a43x11FTFqVHPaqKdT0A3ERgL wlNhVPwVonUz0mpm/F4wq58ONi9kojVz0tDJUJQquqKYhzL6YX9pW2auowPBztTxrNU0 ueSlo4J15LDwwcSAwhHDT80xyLY6T/VCZY4J7ta5nU7E8WUJZQUkOwLQTvox8dAeKJW1 niB+R4nVrjblNkDHMM/P2tMcOBtZgKrsIrlGM8KAG0RVYJRHLwSNZvqabfBqlRGOBOqA 1JjA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732516267; x=1733121067; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yskXsG/Gi9+av4YhT+CVLjJSCJpXUpqc1RCEEwAf/7k=; b=Bqcqw9bBmLfus6XLObRaAqZSqfRQL97Q/UC2IaB5qPWayb1PJnewAvTP39X/fRB7R6 rGkmYDmGU0k1eL812Yct6MTF9+R9coFIvNUL5Ib2r8MaUyfyH0iSwGKUTAb90oa0axeg IERpqM0TzDWPmI0vOphklyqgm20yqJzqonRcA8mPzn2TrzTN4AS8NA9dbC9VEtSbFlvA V8F11d9DNFpyINIGvt7gtezA16/hJHoESpIXhPvk2BUNNiAG1mIomNy8L59Bji6p8nYS BdkIrJb+BAjlw1qb6/KBsByDyemTQk6xy/DVEHwmZp3cAkbWSWcicX2sJOI0B1jdfnzo IXuA== X-Gm-Message-State: AOJu0YyHUBRjdbutxe2kp7+nQifom0N26WzfQonyv6YYuF98nS/MXi3I cYp1gP0bk43vzRhB5Pra6EVf4ADHi3udRViDblWTY6+IvDL0gLnfNXBOvhhcIxBwlneLXIUO8eh X+boiABfxOJuoX1cW+zFmJkrNG5ZBgg== X-Gm-Gg: ASbGnctxeZeH+I2gZvaVY9BDpngyo/PZoqIu58Bn+NUpgBKAgWqH/Oel/uSgWT7zqvD QfFjseB16T1395J3pBIAqUMhcV5ExbbZe X-Google-Smtp-Source: AGHT+IH7DYmBPM6KyP2vGiTjvz4SBNzJkdurpEkrcpQjQA6xuRki7QwjBIBgWGOi8Lz+TqbgWui6c16gRslBdTaN/DM= X-Received: by 2002:a17:906:3cb1:b0:aa5:1ce8:e4e0 with SMTP id a640c23a62f3a-aa51ce8e6a6mr855177666b.10.1732516266717; Sun, 24 Nov 2024 22:31:06 -0800 (PST) MIME-Version: 1.0 From: shashidhar Reddy Date: Mon, 25 Nov 2024 12:00:55 +0530 Message-ID: Subject: Unique key constraint Issue To: pgsql-general Content-Type: multipart/alternative; boundary="000000000000a53a510627b6e0d8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000a53a510627b6e0d8 Content-Type: text/plain; charset="UTF-8" Hello, We have postgresql servers with PostgreSQL 13.10 on Ubuntu release 22.04. The issue is a unique key constraint with two columns one is character another is integer. At some point the unique key did not work as I see duplicate values with these two columns combination and it happened on multiple servers on multiple databases on same table with same unique key. I tried db dump and restore but the key is failing to create when restore with duplicate value errors. --000000000000a53a510627b6e0d8 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

We have postgresql servers with PostgreSQL 13.10=C2=A0 = =C2=A0on Ubuntu release 22.04.

The issue is a unique key constraint with two columns one is charact= er another is integer. At some=C2=A0point the unique key did=C2=A0not work = as I see duplicate values with these two columns combination and it happene= d on multiple servers on multiple databases on same table with same unique = key. I tried db dump and restore but the key is failing to create when rest= ore with duplicate value errors.



--000000000000a53a510627b6e0d8--