Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ooTX3-0000t2-GO for pgsql-admin@arkaria.postgresql.org; Fri, 28 Oct 2022 17:52:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1ooTX1-0003va-Ka for pgsql-admin@arkaria.postgresql.org; Fri, 28 Oct 2022 17:52:35 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ooTX1-0003vQ-85 for pgsql-admin@lists.postgresql.org; Fri, 28 Oct 2022 17:52:35 +0000 Received: from mail-pj1-x102b.google.com ([2607:f8b0:4864:20::102b]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ooTWv-0008E9-2C for pgsql-admin@lists.postgresql.org; Fri, 28 Oct 2022 17:52:34 +0000 Received: by mail-pj1-x102b.google.com with SMTP id t10-20020a17090a4e4a00b0020af4bcae10so5160213pjl.3 for ; Fri, 28 Oct 2022 10:52:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ulSPaMgtYIxqlb6G5D4/rTOp8R3cTw9XYoSwp7kbJeo=; b=MLbIqsBQ6b7KNDUDYssMZMtYv2n06M4yd/ppPLXQ60dymE61O+KFY4PZfgsXh9P8i9 JEjV4794iatBHwa45vbdvov3lwloUozwmRJgt/dURaoxGDaLoKCfGHEG9YaCT4GeP2aR wWQ/K3ogBjFTUWsxqdnMvEeCl72SkM/HcxISVX6RO3PpSkkliMzokhjbGhQCSrQcG7G2 Kj91cZShabSKlwJfnL/urFD/PhDm1SqiRBN/B31VR6u4OPTZV+MvZiHyI0wQgdNpCc9W lfUdwhW6l7pX3s1tQTZCSeuHh0MFCSNQrlkg8i55kpBrPUPMG91JgqI1rbiK5XXg8WwR +1+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:message-id:subject:date:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=ulSPaMgtYIxqlb6G5D4/rTOp8R3cTw9XYoSwp7kbJeo=; b=RFyVRvjlUzowo65BO/Oshh6ITjyHbPZl6YhiiIvdOksPg61fLUznhOyeO13bn8MGPk z7C13N2s5ilMyoeCFxDnjF8ws7Zu9gT42IrNmcTRW4IpFRKHhB/jMcxk2lwSVZztwMos 5wnWoaz7yk1NUwXStnjRF/g+l3CLqa5Cwy8/irKdC1OpbxjASuaSx2BYQ0F3rUPyIHUt yLzgz7SXjn8a5XDgOTCHFgg/xgmrLz4UF8S2fNZENEWps12pLr4EhRKBXwg2oZ9pDDFn LuPgTG8ESywjyVdbaZmG/R6rZ7OCIea6OmZucRh/pHqAe9At9Y6bJEpxu/y8m9r6wT3+ hX0g== X-Gm-Message-State: ACrzQf13VNZHljedyioKpmVNokYNeBV3PVbiQcA4q/nIKZ8Z/Tydy9kC emjzNjdQRYtE4rpnTtfd2+JGibmaEv8AL3CL X-Google-Smtp-Source: AMsMyM5E98Lr5WYlpPl8SdBWg8KVJTC4GbUW4B3s9P5O9JzxJ6wODma5BNBQJta3U+fxwFRnXDTc6g== X-Received: by 2002:a17:902:da82:b0:186:ee5a:47c7 with SMTP id j2-20020a170902da8200b00186ee5a47c7mr176964plx.82.1666979546593; Fri, 28 Oct 2022 10:52:26 -0700 (PDT) Received: from smtpclient.apple (2603-8001-0200-0026-9d7d-a196-018b-8c6b.res6.spectrum.com. [2603:8001:200:26:9d7d:a196:18b:8c6b]) by smtp.gmail.com with ESMTPSA id x15-20020a170902ec8f00b0016c9e5f291bsm3379754plg.111.2022.10.28.10.52.25 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 28 Oct 2022 10:52:26 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: Teja Jakkidi Mime-Version: 1.0 (1.0) Date: Fri, 28 Oct 2022 10:52:24 -0700 Subject: Duplicate data even with primary keys enabled Message-Id: <8A481F39-97D5-4778-AC3C-A34CD29E00AB@gmail.com> To: pgsql-admin X-Mailer: iPhone Mail (19G82) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Admin team, I have an issue where we are seeing duplicate data in one of the tables. The= table has primary key constraint defined on 3columns and we are seeing dupl= icate data in these column data. Is there any way to figure out why this could happen? Also is there a way th= at the primary key constraint can be disabled during inserts?? If so how ca= n we find who disabled it? (Note that audit is not enabled for the table) Please suggest. Thanks, Teja.=