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 1q9jly-0004s3-BA for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jun 2023 10:00:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q9jlx-0005ny-7c for pgsql-bugs@arkaria.postgresql.org; Thu, 15 Jun 2023 10:00:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1q9jlw-0005np-Vb for pgsql-bugs@lists.postgresql.org; Thu, 15 Jun 2023 10:00:08 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1q9jlt-002KAv-7n for pgsql-bugs@lists.postgresql.org; Thu, 15 Jun 2023 10:00:06 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2b1b06af50eso24454731fa.1 for ; Thu, 15 Jun 2023 03:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1686823203; x=1689415203; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=YCrfIO03TDEPdjg40DvZZJASOzlw5H9OSQ1Z6MpJvGY=; b=lGivQL8VtaUpXtd10Wp9RcvqtY1RpCR5MZS4kazC/i0w8Bu+79US24hjTe9/oOJkl7 VDz8x+uHFnsUomfmfGUTDhdkQ2X7N8oaUe2Wpjtxr/IvaQnezUNT/b0G7+SE9rqX1/3z c7QJQqObAqLrGZVLBV+DxSNLfkXbFpjd3ylrQalr4MgMWce4kqRMDugcxsb0BhK7XXct 7Wuj0r/uAfUT6gHJUYQFSqAUnt0u640TIlk0Z5Y+wtD3AqaMk2FbDiMXk82PYYiOJ7Ry wKsIJRiCVXrAcROgtzIvVzv2JpA3B+OEcQLrbCH4kpwG8z89oXC9BMvsBMANZ/5qfHmi RRiA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686823203; x=1689415203; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=YCrfIO03TDEPdjg40DvZZJASOzlw5H9OSQ1Z6MpJvGY=; b=hhSz6Nf5EiEbN8l14W0q2MZUKNwhQqZVyEHlL4TrxGRpzJ7YUcqTg9+ISv6gzuSWCm fBLoBsnTAF0jUSTALc6cN4L/8eU24iZrvwn2IDopOANYGqdidao5L84twGIKfFJdEyhz 056Z15Uwrllo09Fq/Eqm9QL4RpvssdQU5SlNdgxOX/a1NU5WrcTqd24vNszpCpW1JIjC 8srzFee7e16Xr2js3r3//9yhxdRqnZkrW0z0LxPS3t5R12u+4QiMeyStcd1vc+Cb+PKK Xl6/zGudYvcRO4cRHlPSHytr4wRrrjJ3NvxGoMzd2v5He1hZjgUj2ZTEjCm3+YLgMJwz iT6A== X-Gm-Message-State: AC+VfDzDvi8XEuHFuT/xua6PQ6zuSa3hOvJ3/cFiKL51ZjHH0UfcRNu6 XS7CAYGGgrR9nc4phz52ai0= X-Google-Smtp-Source: ACHHUZ78a54biCbvk9TMVPOcs8q87C78+QNxiyyfzjMFJGzwT2mlonWD7qMRC/JZXXOWXpf3Ggi/Pw== X-Received: by 2002:a2e:95d2:0:b0:2b1:daca:676f with SMTP id y18-20020a2e95d2000000b002b1daca676fmr8019693ljh.36.1686823203205; Thu, 15 Jun 2023 03:00:03 -0700 (PDT) Received: from [1.0.0.7] ([178.155.23.108]) by smtp.gmail.com with ESMTPSA id n23-20020a2e86d7000000b002ac78893a9csm3019538ljj.72.2023.06.15.03.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 15 Jun 2023 03:00:01 -0700 (PDT) Message-ID: <02538745-31d0-1f78-f994-86ca794f0466@gmail.com> Date: Thu, 15 Jun 2023 13:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: BUG #17888: Incorrect memory access in gist__int_ops for an input array with many elements Content-Language: en-US To: Michael Paquier Cc: Richard Guo , Ankit Kumar Pandey , David Rowley , Teodor Sigaev , pgsql-bugs@lists.postgresql.org References: <17888-f72930e6b5ce8c14@postgresql.org> From: Alexander Lakhin 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 Hi Michael, 15.06.2023 07:53, Michael Paquier wrote: > I have spent some time on that today, and applied what has been > suggested to restrict the usage of this operator when inserting data > for a leaf page, so as the decompression does not get crazy when > retrieving the contents of the leaf pages. Thank you for paying attention to it! I closed https://commitfest.postgresql.org/43/4280/ as committed. The confusing message I noted previously: ERROR:  index row size 8040 exceeds maximum 8152 for index "test_idx" is not emitted now, although I think it still can be produced for some other gist indexes. But that's a matter for another day, I suppose. Best regards, Alexander