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 1qDFyz-00064H-Ds for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Jun 2023 03:00:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1qDFyx-0007bG-Dm for pgsql-bugs@arkaria.postgresql.org; Sun, 25 Jun 2023 03:00:07 +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 1qDFyx-0007b6-4z for pgsql-bugs@lists.postgresql.org; Sun, 25 Jun 2023 03:00:07 +0000 Received: from mail-lf1-x134.google.com ([2a00:1450:4864:20::134]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qDFyu-000JlW-7n for pgsql-bugs@lists.postgresql.org; Sun, 25 Jun 2023 03:00:06 +0000 Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-4f7677a94d1so2798434e87.0 for ; Sat, 24 Jun 2023 20:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687662003; x=1690254003; 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=wPJLLfPA4UToy2d0nqoCEHjj+S5xRr2ElSK2wLoWtlc=; b=nXoJYraCxHevcfiTQhZpDpHKVp4omLNyPd7aFC+iiDDktTRJmwMZ8ZS7d2MkxYOz18 RbGVcomaEgXn3FOpf7TviZZbQDIJzQZEFxIemEa1UFElF117fX0cu0WtPXGvfAzqdNGt oXzKJt6PXSB/hVBNXv52NEJ36PzhIxpKJvgYJPNfGzko65V3es8QMhYtPdqVC/NJ8CN2 xNXhLDwGedYIp8RZpodgP8teVxA3YrzWo1I5rsiNmYg0JpkUkw6w6rnoTFJF9xnyET6s VrR7CGVZIwZMYLKb3mnuVhVjBE0XDtQidbEXJ47AcEaB8LiK6e8lkdnEV5SWPpRzT7/T Epxw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687662003; x=1690254003; 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=wPJLLfPA4UToy2d0nqoCEHjj+S5xRr2ElSK2wLoWtlc=; b=MUAhBgz4BeGn5BVavkVDmoUH6mCPvj0c94nQowkh9hSbb3prXCiSvK6HAUkNgolrIS kzyKKsZrtnEUx6+0lmU9VtuTmlP7nrGJ98MGYOd8TRbQgEXxxHLW7qP9Y2EUUyaW16OO m7ucAkBW6634RMZHWnaQGDFAN3bqPYUZbOwVvZxQaW/COvEgZhDDuK1+y+bRncTHNUuK y3S6YR8sfsYTktN3N6UVaqO49oMX+Ajf+pmFhvMCAO6xKb9DxS25qimq2cX/0iHEmqkn ER6ithfvd4RS78QLy93Fjrm+F/azase2Mh47CQffJjf/O7dlCcdWq8cfqmFVrTZa1QdY dKrQ== X-Gm-Message-State: AC+VfDyE7EqN4fW3Qkuxal3xyb0a88EYAEdQf8x+t3KMmFQBQHGNA4hE gegHATlUUlE2sG658BW4hnM= X-Google-Smtp-Source: ACHHUZ4WRxvV6NAAMGSWRVj3rS4oM6e8UvWsvxKs/CcLXfC9BnqVcq5XgnOZQeCTqtGd5mkkCClyaA== X-Received: by 2002:a05:6512:ea7:b0:4f5:bc59:6f21 with SMTP id bi39-20020a0565120ea700b004f5bc596f21mr15762367lfb.12.1687662002787; Sat, 24 Jun 2023 20:00:02 -0700 (PDT) Received: from [1.0.0.7] ([178.155.23.108]) by smtp.gmail.com with ESMTPSA id eq6-20020a056512488600b004f86d546458sm486416lfb.6.2023.06.24.20.00.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 24 Jun 2023 20:00:01 -0700 (PDT) Message-ID: <68148dac-a574-f421-2905-51ebde2fe000@gmail.com> Date: Sun, 25 Jun 2023 06: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 #17995: Segmentation fault caused by UPDATE statement Content-Language: en-US To: Tom Lane , zuming.jiang@inf.ethz.ch Cc: pgsql-bugs@lists.postgresql.org References: <17995-9f20ff3e6389db4c@postgresql.org> <285547.1687636319@sss.pgh.pa.us> From: Alexander Lakhin In-Reply-To: <285547.1687636319@sss.pgh.pa.us> 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, 24.06.2023 22:51, Tom Lane wrote: > Hmm, I don't think this is about the UPDATE per se, it's about > not having a stack depth check in TParserGet() :-( BTW, there is a commitfest entry to eliminate a bunch of other stack overflow hazards (may be the fuzzer can find some of them too): https://commitfest.postgresql.org/43/4239/ (It looks like this issue was not discovered there because TParserGet() doesn't call itself directly.) Best regards, Alexander