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 1pQAH7-0001JD-Oe for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 16:59:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pQAH6-0004PI-KP for pgsql-general@arkaria.postgresql.org; Thu, 09 Feb 2023 16:59:56 +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 1pQAH6-0004P5-9t for pgsql-general@lists.postgresql.org; Thu, 09 Feb 2023 16:59:56 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pQAH0-0005sU-86 for pgsql-general@lists.postgresql.org; Thu, 09 Feb 2023 16:59:55 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 331B35C028A; Thu, 9 Feb 2023 11:59:49 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 09 Feb 2023 11:59:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding: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=fm3; t=1675961989; x= 1676048389; bh=1f7w9IFJtUH4DhvJQaxxaeEE8oKz6YUUnaO0l4lv/I4=; b=N rv7FADAp8dNES4UIed/B5cZH4nOgBtszCo6rEpzKQIlN/CLIdyqFMtO78B9Y1cO+ +zUuKofx9pKmoVdLCpUXybKSOC24m+cBVV5dglHPFg5LKaK5lHEVUpb0HxXl5r0F 8dpB0wWTFjevNUNwCIZC1wvWkUOOq/XnMyTAFvLcrW/jyH4wzPX1CgIluOOSf/E4 U0RpiAx7nH63ZmLosRYEcRi2WpP0IqG5Ee3QOdzOrn+L+cW5PLAP+kSqH4VHZ7Vp 1em89o96vDtP2VpeYQd635239lu5bf6VZDgUdpdfmPlenP65BTrZZ6PkG8ONnmby Bu9u5Nk6s55yMl8WBNETw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding: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=fm1; t=1675961989; x=1676048389; bh=1 f7w9IFJtUH4DhvJQaxxaeEE8oKz6YUUnaO0l4lv/I4=; b=ZbsQW77IZWZ8A8dCH bPX52LCV70RVopWKFeo5P4epsg99D6aBQDkeFCU+dKJ840yAPCMMQC9pQc2YKjMh kUaKJm9e9RGX7AG8shuoqJbGPKkzF0ExGrYRkkmONXxcvKjgtMlrSyzYTA9btOYV 6iIbWmeG2kXBGJNtOEUok4CUSVZDbJT0kbw+sb7R7HhKlHn8ojzJ8tICHPYDvaUQ zn4sjSYj7MRR35y1OgqH8MfJ85etnVjvnN84AcNDYs0vXessrjxvIw8APvSlIlDt weX3WNveT5/WUnd4VjCBTFNt5+4CgblPednwtItHI4XhFr2KZVYHqjjml1dKF2GH jv1Fg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrudehfedgleefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttdefjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpedugfeuleegveffhfegleejhefhtedtgeeileeggfeh fefffeevgeejtdeutefftdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmh grihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 9 Feb 2023 11:59:48 -0500 (EST) Message-ID: <3918b771-34c7-d6ca-20a8-eb07c2de6817@aklaver.com> Date: Thu, 9 Feb 2023 08:59:48 -0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 Subject: Re: ERROR: posting list tuple with 2 items cannot be split at offset 17 Content-Language: en-US To: Paul McGarry , pgsql-general@lists.postgresql.org 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 2/8/23 23:53, Paul McGarry wrote: > I have three databases, two of databases where I am experiencing the > issue below. > > The first database was created from a dump in Feb 2022 (a few weeks > after the time period for which I seem to have problematic indexes, maybe). > The second database was then cloned from the first (ie filesystem level > copy) soon after. What where the commands for the dump/restore? Second database, same machine or different one? > Since then all databases have undergone a number of minor version > upgrades, including to 13.9 and an OS update last week for the two > problem databases (the other is still on 13.8). The OS's and the update to? > > Now, a process which does clears some data > 13 months old is getting an > error when trying to do that update. > > My suspicion is that either: > - there was probably an issue with the index 12 months ago and that > problem was copied when I cloned the database, and is just becoming > apparent now a script is accessing 13 month olf data. > - something in our recent upgrade has caused the problem. A dump/restore would recreate the index at the restore. > > The third database is still on 13.8, and with some OS updates pending, > and is not experiencing the problem. I'm betting OS change as culprit. > > Any suggestions on what else I should look into, in particular anything > I should check before upgrading the remaining 13.8 DB to 13.9? > > Thanks for any help, > > Paul -- Adrian Klaver adrian.klaver@aklaver.com