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 1ihaka-0008M8-Uj for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Dec 2019 14:56:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ihajb-0007C5-Be for pgsql-bugs@arkaria.postgresql.org; Wed, 18 Dec 2019 14:55:31 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1ihaja-0007By-SH for pgsql-bugs@lists.postgresql.org; Wed, 18 Dec 2019 14:55:31 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1ihajV-0000xn-Qv for pgsql-bugs@lists.postgresql.org; Wed, 18 Dec 2019 14:55:29 +0000 Received: by mail-wm1-x342.google.com with SMTP id t14so2211262wmi.5 for ; Wed, 18 Dec 2019 06:55:25 -0800 (PST) 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; bh=Q5Py5+f2Zwn35AKfZpEM8Mn8K7w/9SfjAvWLKrPwbQk=; b=o2T025/emudLhBD5xARPkeQWIZBY+b7ZpyUWdBpkUgh2ToILIMk/j4/eSM76lp5eYO c6f6UqSZ9phseE6w720MSP8xUNYvVgHJoKKtFimFedqQZBTO/CzZb8qr/hgnEDW8Cvkk 6+3DBnsR4LuGJuwcdWs59i014y3bcCjB137dPMntxNUVAA7DY2Furf+APDOdPOXJ47B6 FG8OZ9VDs1PeRqigCvzBuhuTDsn3+w3Au9VV/PfXglHX37UVGFiYjOmPRBrWgx5rc2fx puFwkzU6/8aIziajlryixG4oNBqtNuq1XME9xuW+URNipCoHua4+0v1YjYclB8ceoN44 deNA== 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; bh=Q5Py5+f2Zwn35AKfZpEM8Mn8K7w/9SfjAvWLKrPwbQk=; b=sDOunX6X+4H+1Z+UKzE72wNCCLV06FsZcD6vlfvP8pKLqeb1NaDeADhJxQJ2qscvBJ I6Zj6BQSirr7iNuryU3ntFlvOHtdP6zla7yMh/5XGOaEHaR0WY9SB09ZR5t7mVmfkNvD cAZahMZgSFFOSq88bPyNhopK3w1+I4iDf7df1siKxKwtyTt5DpGxraNRnOLKb+w6lseJ ojf0ZKagbLtsdKAXW2A+r100Q8kdTSKf9aNnwCiYmWB+gOla7XOBPoTsvByFr4lpb5Lj 6GEfeVwH6qxIY1F+fXSeAk+VvzjN0dSTFmNPDO3lSwctjeNRkALxYz83OZLymD7Jb/ky gBhQ== X-Gm-Message-State: APjAAAWFqlN9JcBnQn21iy4BJoxzjVbho5gOj8/35v24vxDniSqUhRer lyRveR8Fgf7kVKxCFHLXrEc+Vg== X-Google-Smtp-Source: APXvYqwspZ1/2j9llJNO6pBA5uQwsmpc5sCnMh/TEXZZ3wb9t0Q6vWK0GV+yGShJkR37UI5+AqSHXA== X-Received: by 2002:a1c:9c87:: with SMTP id f129mr3698840wme.26.1576680923938; Wed, 18 Dec 2019 06:55:23 -0800 (PST) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id g17sm2621032wmc.37.2019.12.18.06.55.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 18 Dec 2019 06:55:23 -0800 (PST) Date: Wed, 18 Dec 2019 15:55:21 +0100 From: Tomas Vondra To: Roman Cervenak Cc: Tom Lane , pgsql-bugs@lists.postgresql.org Subject: Re: Memory leak (possibly connected to postgis) leading to server crash Message-ID: <20191218145521.oyhvjn5ptf3a6ej4@development> References: <20191206124119.qe2xaffcbkcbmve3@development> <18069.1576082949@sss.pgh.pa.us> <20191213132036.3m27dlquaxoorkja@development> <20191217125035.wdplskovliz7d5lh@development> <20191217180957.akh7vyex5guxqs7r@development> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Dec 18, 2019 at 09:49:22AM +0100, Roman Cervenak wrote: >Sure, here it is, 10k queries generated by this tool: >https://sygicpublic.blob.core.windows.net/postgres-bug-data/postgis_memory_leak_queries.txt > Thanks. I've tried running this on current branches (so PostgreSQL 13dev and PostGIS 3.1.0dev), but that does not seem to be leaking so far. I'll leave running it for a bit longer and then I'll try running it on 12.1 and 3.0.0 which I think are the versions you reported. I don't have an Ubuntu box at hand, so I'll have to build it locally, though. BTW it's customary to reply in-line here, top-posting makes it harder to follow the discussion etc. regards >RC > >On Tue, Dec 17, 2019 at 7:10 PM Tomas Vondra >wrote: > >> On Tue, Dec 17, 2019 at 02:20:41PM +0100, Roman Cervenak wrote: >> >.NET core is cross platform, you can run it under windows or linux, just >> >install .net core runtime. >> >> That's possible, but I have zero experience with .net core, and >> unfortunately I have no system with it installed. I've tried running it >> under mono I just installed, but quickly ran into issue that I don't >> know how to solve. I'm willing to spend time investigating the issue, >> but this seems a bit too much ... >> >> >I did not try to run loop with fixed params, I tried to mimic my >> production >> >workload (which is not random of course, but highly variable by location). >> >You can certainly try. >> > >> >> Can you capture a couple of queries, and share those? I'll run that >> under valgrind and see if that produces something interesting. >> >> >> regards >> >> -- >> Tomas Vondra http://www.2ndQuadrant.com >> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services >> -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services