John Gemignani

@vladiksun I do see the memory leak you are talking about and have narrowed it down to a few commands.

@vladiksun PR #2028 Should address most of the issue with this memory leak. Although, there might be more, more subtle leaks.

@vladiksun It is in the master branch right now. I'll be making PRs for the other branches today.

@vladiksun This fix is now in all branches. If you want to test the latest for the branch you are using, try `dev_snapshot_`. For example, `dev_snapshot_P14`.

@vladiksun There are some other memory leaks, for example #2046 which I am currently working on, that could be contributing factors. That particular one highlights quite a few other areas...

> Oh! My bad! Thanks so much for pointing out. Will take a look and fix. > > I will run the regression tests again. The last time I ran...

> I think these changes help add clarity to the process and the small grammar issue I noted can be cleaned up in a future commit if @jccampagne is unable...

@alexgraul It is a possibility, but our team is very stretched atm. Additionally, we're working on getting some important improvements and bug fixes out, prior to the next release.

@alexgraul I meant to link this here - https://github.com/apache/age/issues/2111#issuecomment-2441903180

Yep, verified this is an issue with 1.1.0 - ``` psql-11.5-5432-pgsql=# drop extension age cascade; create extension age; load 'age'; set search_path TO ag_catalog; ERROR: extension "age" does not exist...