Rafia Sabih

Not seen again, hence closing.

Hey there @joeyberkovitz it will be helpful for us to progress on this one if you could provide some script or standalone steps for reproducing this issue.

@genedavis Thanks for reporting this, could you also give some standalone script or steps to reproduce this issue, so that we can look into this further.

I am able to reproduce the issue with the following set of commands, ``` Create extension timescaledb; Create table test_mem_leak(col_1 text, col_2 int); Select create_hypertable('test_mem_leak', 'col_2', chunk_time_interval =>10000) ; Insert...

Update: 1. When I increased the chunk size so that only a few big chunks were there, the memory was NOT consumed significantly. 2. When I created normal partitioned tables...

I tried reproducing this bug with lesser number of chunks, but unfortunately I found no oom or other issues. My table schema and size is as follows, ```SELECT * FROM...

@michael-sayapin Thank you for taking the time to report this, but we would need more information in order to proceed. Firstly, a complete set of steps to reproduce the issue...

:+1:

I tried to reproduce this issue but unfortunately could not. I was doing following: `create schema _prom_catalog;` `CREATE OR REPLACE PROCEDURE _prom_catalog.test(rollup_schema TEXT, table_name TEXT, resolution INTERVAL) AS $$ BEGIN...