Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHDob-0002UP-3a for pgsql-performance@arkaria.postgresql.org; Sun, 06 Oct 2019 21:11:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iHDoZ-00087E-Sw for pgsql-performance@arkaria.postgresql.org; Sun, 06 Oct 2019 21:11:39 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHDoZ-00086q-JY for pgsql-performance@lists.postgresql.org; Sun, 06 Oct 2019 21:11:39 +0000 Received: from mail-wm1-x331.google.com ([2a00:1450:4864:20::331]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iHDoV-0006NE-Io for pgsql-performance@lists.postgresql.org; Sun, 06 Oct 2019 21:11:38 +0000 Received: by mail-wm1-x331.google.com with SMTP id y135so13432318wmc.1 for ; Sun, 06 Oct 2019 14:11:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=IAAI77i24Qw4sHPzb4WC1WTJf0ngKZnSTynx6V5w7tw=; b=XORUYS4bPiTW+K4RtgZtIpdf8qK8REf4EgaLziMcKdYhWTbJRS2f5MUUtFv0J9nPGT 1kIfeg7zMT60tF74psvsXhPbgC0BsFR3F0kLLP2H+Yp1omP/YwN8lUDNX76T51G4GYoQ S9yZQ6beQxoLgolDV0BtX1OYtUscwdkS81HS/5m7bSH1kNoSw6uAMMorpxajg0YRrbCj pEHXc9jENQJ5PN7GLfOqBJJyoNA9DziAKCvc+viH7MlFZSbLrPQNFMauVGG936KdsYUi 0xquSKRZdFZgWhVBbkIXLfQS5d2NOJ4UpDEgfeZUiUUSSY81p5soOgpl/Jq65SeCR+Vh 2uNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=IAAI77i24Qw4sHPzb4WC1WTJf0ngKZnSTynx6V5w7tw=; b=Ya/6f3Y/oQyTKiwjDKi9bbFDzo+O8JSaCdT/3T1qFf+4Y4EvWow2C4fyhiKcX3P2Ta AgzEbPuRpKhA1EWC15Sa7eEzyZB4OCTz6m8P2bcHztWT7cwYjuk3Bl8kAR0tuzGqva4h uxiflQhTSccy8Pc89CR5ewr4bQA21ZTsHVCWC+zVZ/VTw5YM1sZc6G3xlbRFo2DdeyLq 6xgOVrRY4yW0oHbFh7QHLJ4bqNAG8NoPS9pXuhSMCPDZ3/EtjdaAVIOyTJbuwzRgYED5 uPC6Y3Kb0chtGB7yKnoetheBaCx5l7scd1qnszgf8Sc6PwDvL4UGbdJgfmGk9kQDj3V4 bj4A== X-Gm-Message-State: APjAAAVUoxGHkc2Vz8d5beSXiqJzmXJS6O0TL/tJzKyRSWJln1QJa4LK c9mCbHnDnkOCTmD5jkq73I3+HQ== X-Google-Smtp-Source: APXvYqw3U3pNaA2gI1ztuXqs4gEAIZDaxwdnKUPB+tp8yO/KEwkJiQFwqYqszOkHeEm72LNij6HWjw== X-Received: by 2002:a7b:cd88:: with SMTP id y8mr13824422wmj.1.1570396293357; Sun, 06 Oct 2019 14:11:33 -0700 (PDT) Received: from localhost (ip-86-49-253-183.net.upcbroadband.cz. [86.49.253.183]) by smtp.gmail.com with ESMTPSA id r6sm13843481wmh.38.2019.10.06.14.11.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 06 Oct 2019 14:11:32 -0700 (PDT) Date: Sun, 6 Oct 2019 23:11:31 +0200 From: Tomas Vondra To: Gunther Cc: Justin Pryzby , Tom Lane , Jeff Janes , pgsql-performance@lists.postgresql.org, Alvaro Herrera Subject: Re: Out of Memory errors are frustrating as heck! Message-ID: <20191006211131.5qpvj5dfh6f4ybfq@development> References: <20190421161434.4hedytsadpbnglgk@development> <19198.1555857403@sss.pgh.pa.us> <20190421164022.GD14223@telsasoft.com> <20190422030927.3huxq7gghms4kmf4@development> <2d422e7e-3105-3320-f3d5-801bd6a8b27d@gusw.net> <20190423204348.GJ3925@telsasoft.com> <20190424003633.ruvhbv5ro3fawo67@development> <20190428141901.5dsbge2ka3rxmpk6@development> <7ed3d2a0-0a1d-0bd2-5417-9b69038abfcf@gusw.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <7ed3d2a0-0a1d-0bd2-5417-9b69038abfcf@gusw.net> User-Agent: NeoMutt/20180716 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Aug 23, 2019 at 09:17:38AM -0400, Gunther wrote: >Hi all, I am connecting to a discussion back from April this year. My >data has grown and now I am running into new out of memory situations. >Meanwhile the world turned from 11.2 to 11.5 which I just installed >only to find the same out of memory error. > As Tom already said, this seems like a quite independent issue. Next time it'd be better to share it in a new thread, not to mix it up with the old discussion. >Have any of the things discussed and proposed, especially this last >one by Tomas Vondra, been applied to the 11 releases? Should I try >these older patches from April? > Unfortunately, no. We're still discussing what would be the right fix (it's rather tricky and the patches I shared were way too experimental for that). But I'm pretty sure whatever we end up doing it's going to be way too invasive for backpatch. I.e. the older branches will likely have this issue until EOL. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services