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 1qNGwa-004X0C-5f for pgsql-general@arkaria.postgresql.org; Sat, 22 Jul 2023 18:03:04 +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 1qNGwY-00GDxF-74 for pgsql-general@arkaria.postgresql.org; Sat, 22 Jul 2023 18:03:02 +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 1qNGwW-00GDx7-HQ for pgsql-general@lists.postgresql.org; Sat, 22 Jul 2023 18:03:01 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qNGwT-000tZO-7e for pgsql-general@lists.postgresql.org; Sat, 22 Jul 2023 18:02:59 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 0E8E05C009B; Sat, 22 Jul 2023 14:02:55 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Sat, 22 Jul 2023 14:02:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1690048975; x=1690135375; bh=zsD5Vh2R5VZntKfHKSihqIBJdfdDH3mLvro 7fsqF2wI=; b=Mull6AVCcK/i1UcnlJ+H9khGzIiDP/ghETgr1zgxQPuhp5W5n1j +BJEJSpCF4mdl2ADvhUXIBBUrH2ZSdxsFZKzTfnpuK19QUOVSOEafDdEWNq3VnAT DOLwA9Wz2scDWCorA+ULYONwHBljH3+ZU275ZMwt2sXf4e43YHY6ouNNlYcFSkio z/aSeEeG1a8XkEroJ/l8c1nK6dEFIxVF81Tz9aGNYLnOAwjxqybwrJOGdzOY7VTP O0Gr2AHdvcLaSmHblNmRtj/PY6f6N8El7+7BYGbc2Wj0W4c3VEb7vaK9d8Nk/MCP qFsAoRSL/wvbIoN7sOMNYido/qQbom1KApw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1690048975; x=1690135375; bh=zsD5Vh2R5VZntKfHKSihqIBJdfdDH3mLvro 7fsqF2wI=; b=be+/xFxs4ifvUnqi5s7k9f/Qt/7dFVscgyLNRaopm7puqfPwF2G sqvE+ry3KGmgKRr1LkTdu7vKcEE9iwO//qpBUlk75pLqF/l6A3/7yEVpsRyssM2p 0mc+701mEXUXjTv0jh4z4NvJgP0ZpJ/ZqHdjUhUBVWBi5fMAW9NDg6LlbQJn73Mp pqkXDzuINHx3ns8MSUH2QFsTN2BOkBkHBnEZDNdP+sbfkTPNAoKXUT1bFIKti3LQ FT43LgyydaJNy/Hdc6RSX6qZilHyWyDdaohZCQB5xP4i9X4h7Dky3+V4vZzAakU/ ELf4FyvOAogFd13rnsk28LGrN2MEHkloyKw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrheeggdduudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpeetughr ihgrnhcumfhlrghvvghruceorggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtg homheqnecuggftrfgrthhtvghrnhephedugfethfettdehieevteeukedtjedvhfevkefg udefgeevteduvdeuvdeggeegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpe hmrghilhhfrhhomheprggurhhirghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sat, 22 Jul 2023 14:02:53 -0400 (EDT) Message-ID: Date: Sat, 22 Jul 2023 11:02:52 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Duplicate Primary keys in postgresql tables Content-Language: en-US To: De Lan , pgsql-general@lists.postgresql.org Cc: Amit Virmani , Terence Yim , Vitalii Tymchyshyn , Samik Gupta , Albert Shau References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 7/22/23 10:11, De Lan wrote: > Hi pgsql community, > > Recently we found in a postgresql 11.19.0 alpine table there are two > rows with duplicate primary keys. > > > *Our questions:* > > Any ideas on what might cause this behavior other than the collation? if > it is a well-known issue in the pgsql community or it really is the > coalition that's the root cause, do we have mitigation for this kind of > issue from happening in future? Don't blindly update containers, test first. > > > > De, > > Thanks! > > > -- Adrian Klaver adrian.klaver@aklaver.com