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 1qixkR-008fI0-40 for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Sep 2023 14:00:11 +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 1qixkP-000JAF-Dw for pgsql-bugs@arkaria.postgresql.org; Wed, 20 Sep 2023 14:00:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qixkP-000JA1-4Y for pgsql-bugs@lists.postgresql.org; Wed, 20 Sep 2023 14:00:09 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qixkK-006KOA-7f for pgsql-bugs@lists.postgresql.org; Wed, 20 Sep 2023 14:00:08 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2c0179f9043so48653051fa.1 for ; Wed, 20 Sep 2023 07:00:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1695218403; x=1695823203; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id:from:to :cc:subject:date:message-id:reply-to; bh=kikqWnnegNpKEecpaQ7C/oruSCEKEPjnFG2KgsRMmps=; b=l4E+M2lBiBAOehGg+DyE5cV5UIig6xXQjmjvzGew8stFFEIg9DySJvFBlbLPLM8J/e IX7/YBb9LTV8TL39UkM1Ed6Y/xChFa8fhaZQfD+g2n/Z5p37VfjJzOsWeSqG23Xdx0YF 3mwCEeIOG3tAR3LCkXBw9aDRrMKUXMDtSFLU06rC01JaUinr0uGOBVexXn/5txhOlt2e UnD3YrNsBG6mpRImRjCDI35+QE+mBMnXZhShVKQ5Hf6cxhhsLCziGpIWS25WkwngAaza yMjUe7U9JAW5SxWzoiPLv+2Cru2QqgkunYMIegquhCr09dNL/s6CFOAzxzJHlW8LQ2rr yUMQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695218403; x=1695823203; h=content-transfer-encoding:in-reply-to:content-language:references :cc:to:subject:from:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=kikqWnnegNpKEecpaQ7C/oruSCEKEPjnFG2KgsRMmps=; b=FgtNvnoclasts9OySp5V/r0tuUByn3HWfogj1qL+WfHo0Fq4Z1BNxEHBV1nOiP71BX 5CtgQynJjjx9ZZQBsls9HK2cNBWTPAPTozp50M+EzWF+BnNc7R/n6/xAg0I65CdZYEgX mapymRVYSdce45rMJHsx5A9Rffzw6JUaPnWPd2SGSQ//71P1GXFgfcPGZVc6nOtcCwgq JPkbDmxMHhTQGJRpOfC2td7ehsAlp1XAMyWcx7YDaxz78wRGbTFtHUplHsVW5OUC5KLu j1Qi/GIqd+VHEjR9BldnhyLwu7pomXImBE6/M269TsOBONe27sQRyULy7EgHyPh2wTc1 /jEA== X-Gm-Message-State: AOJu0Yyf4hyKFQx8HOJcm10hmCsgizLr5iOLp1tWSxmmK0MVpgUoSGsm x8AC294d4LE7sEXtSvCcAs4= X-Google-Smtp-Source: AGHT+IEZEObTKPQEn0IHVOG3KDWas7ul7tpIchhUPar/KTNJURO73uZSWwjO4Dfj+aOSW/ZDKXKPig== X-Received: by 2002:a2e:9181:0:b0:2bc:f28f:9147 with SMTP id f1-20020a2e9181000000b002bcf28f9147mr2497965ljg.48.1695218402730; Wed, 20 Sep 2023 07:00:02 -0700 (PDT) Received: from [1.0.0.7] ([91.185.77.225]) by smtp.gmail.com with ESMTPSA id v5-20020a2e7a05000000b002bcda31af28sm3119295ljc.42.2023.09.20.07.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 20 Sep 2023 07:00:01 -0700 (PDT) Message-ID: Date: Wed, 20 Sep 2023 17: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 From: Alexander Lakhin Subject: Re: BUG #17798: Incorrect memory access occurs when using BEFORE ROW UPDATE trigger To: Tom Lane Cc: pgsql-bugs@lists.postgresql.org, Richard Guo , Andres Freund , Peter Geoghegan References: <17798-0907404928dcf0dd@postgresql.org> <87fe6c28-80b2-f709-a8db-d105e5240e39@gmail.com> <1849610.1682807087@sss.pgh.pa.us> Content-Language: en-US In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Tom, 09.07.2023 18:00, Alexander Lakhin wrote: > > 30.04.2023 01:24, Tom Lane wrote: > >> Bottom line is that I'm afraid the present patch is band-aiding a >> specific problem without solving the general case. > > The next one is more generic, but still limited to the ExecBRUpdateTriggers() > bounds, as I still see no problem outside. > If this issue is not approaching the top of your todo list yet and you don't mind, I'll queue this patch on the commitfest. Best regards, Alexander