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 1pUv1A-0002aG-2y for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2023 19:43:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pUv18-0004tJ-UA for pgsql-bugs@arkaria.postgresql.org; Wed, 22 Feb 2023 19:43:06 +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 1pUv18-0004t9-MQ for pgsql-bugs@lists.postgresql.org; Wed, 22 Feb 2023 19:43:06 +0000 Received: from mail-io1-xd35.google.com ([2607:f8b0:4864:20::d35]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pUv16-0006gQ-Cr for pgsql-bugs@lists.postgresql.org; Wed, 22 Feb 2023 19:43:06 +0000 Received: by mail-io1-xd35.google.com with SMTP id y140so4268791iof.6 for ; Wed, 22 Feb 2023 11:43:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=/ql2iSn/wwlA88dz49DStNmhBzDEWMLtYF15VlFNIuw=; b=VEidHktUxetkfUlri3+3X+nZ+hqFbvrNkhBHwPHjtXCXY/50ZTJ/8Iy8sm1RWhFm2P vruJF1i5flHk2JJyyGdAEqmz43qQ+XU4m9ssct36K+gsASXy1wusmq0W2FB95SGb4UPV 1FKFuccfoAdB4BcHi2M0/UXhzx+DESDJznFh9ZVnOPfcd9eEvVof1BGIa2bxyD5T+V2O VXP/wE/eZA3U3NA93S5c1ZU5GrHH+qvglhs2F79CnvMltv6iE53F/KeIm3ZzRqxPnfm5 Gr9A2wEsj2hXB7xjvdEV6DjcxChxXQwuwfrCW0phOU98J0nnEsmCGSs8S1BenM/kSqCh E7/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=/ql2iSn/wwlA88dz49DStNmhBzDEWMLtYF15VlFNIuw=; b=mBTJ4nVvUSqOK4vbLE3BOWZdSwfpVnjGc5klRyjvo9WNohMWLte2Im+Pb9DatV7RKI 7dkbRU01zln4CCqGCwUIyf99OdGDS1NtxfBbKnXExAkDpCsoR2kFg5+b5NueSt1t3q31 ccZMGj75xo4Df/GqI1Rkya65EmvYvqOEpjKeSxCO9UNphabQWWAmM0nT+ek8e6Njwwun wN3yBPJ7VrZ8Bxw4JWdciUpLsLd18U7OHgE+cn+Iaj0s6GotPBvc9JXbs343loWRsuzn 3Vv0/jNc+79M5lm0+WPo1FHkyDak0Of7Xk6mlXx9txcMwfPX1xRw6n5E9PMzTP/dVSzl qOng== X-Gm-Message-State: AO0yUKX7bnAhku/BTRc0GY3wSSoxBsmaG1S2S3hhNDTZIwWZHtYHNzlm UiLmc3BZpRJ6gLRDOD2oXCV4eg== X-Google-Smtp-Source: AK7set9VFbz5vH+nd3ZHlTzUCSI6s7heyh3K7fvhyWoaXA2Eqd/G1RN1rsSQrJuPIVv7bApJCkCQdA== X-Received: by 2002:a5d:9859:0:b0:71a:b85c:2995 with SMTP id p25-20020a5d9859000000b0071ab85c2995mr1799236ios.15.1677094982597; Wed, 22 Feb 2023 11:43:02 -0800 (PST) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id s9-20020a02cc89000000b003e5a7d97b84sm142034jap.95.2023.02.22.11.43.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 22 Feb 2023 11:43:02 -0800 (PST) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id B5CE1800386; Wed, 22 Feb 2023 13:43:00 -0600 (CST) Date: Wed, 22 Feb 2023 13:43:00 -0600 From: Justin Pryzby To: Andres Freund Cc: Tom Lane , David Rowley , lauri.laanmets@eesti.ee, pgsql-bugs@lists.postgresql.org Subject: Re: Memory leak on subquery as scalar operand Message-ID: <20230222194300.GF1653@telsasoft.com> References: <1046179.1667263449@sss.pgh.pa.us> <1073512.1667275802@sss.pgh.pa.us> <1084048.1667278336@sss.pgh.pa.us> <20221101055132.pjjsvlkeo4stbjkq@awork3.anarazel.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20221101055132.pjjsvlkeo4stbjkq@awork3.anarazel.de> User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Oct 31, 2022 at 10:51:32PM -0700, Andres Freund wrote: > Hi, > > On 2022-11-01 00:52:16 -0400, Tom Lane wrote: > > David Rowley writes: > > > The single subquery version also crashes for me, so perhaps it's just > > > the amount of memory that's being used and when the OOM killer is > > > triggering. > > > It crashes even when I set jit_inline_above_cost and > > > jit_optimize_above_cost above the query's cost. > > > > Hmm, maybe we're not seeing the same thing? > > I can't reproduce that either. @David: does the query really crash as you described - with neither jit inlining nor optimization ? Is it due to OOM or something else ? Does it crash with/without Andres' patches ? What version were you testing ? -- Justin