Re: BUG #16363: Memory increases for each table accessed until connection is closed

From: Eduardo Barreto Alexandre <sezdocs(at)gmail(dot)com>
To: luis(dot)roberto(at)siscobra(dot)com(dot)br
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16363: Memory increases for each table accessed until connection is closed
Date: 2020-04-17 19:17:10
Message-ID: CAG6JkqPH+-S5BBdJhnrzgK10R7NsnBVo0GqF09XRtF6YXrTkhw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Actually, I take it back, I did the 1 connection wrong.. Doing the
connection directly didn't trigger the problem.

Thanks Luis, your suggestion made me close the scope in the issue! It was
actually a cache done by default by Ecto (Elixir's database library), I
just created an issue in Ecto's github
https://github.com/elixir-ecto/ecto/issues/3284 and got the response
confirming it and also the fix to disable it.

Thanks you all very much for the help!

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2020-04-17 19:44:26 Re: BUG #16375: Error in pgAdmin 4.20 when trying to script a function to Query Tool
Previous Message PG Bug reporting form 2020-04-17 18:33:25 BUG #16375: Error in pgAdmin 4.20 when trying to script a function to Query Tool