Zsolt Horvath

hey @boxhock any chance to provide a [stack trace](https://github.com/timescale/timescaledb/issues/4418#issuecomment-1147182129) for us? Also, can you please share with us the exact schemes of the tables you used for reproducing the issue...

HI @BilalS10 thanks for describing this issue, which is quite a tricky one. In order to be able to reproduce the issue we would like to do the exact same...

Thank you @BilalS10 sending these details, from the explain output it can be seen that there were many chunks involved in the deletion, which can answer the question of the...

Hi @BilalS10 , TBH, I'm struggling with reproducing your case, unfortunately. I used the same setup and settings as you, generated the same amount of data, executed the same delete...

Yes, the amount of available physical memory explains why the OOM killer was triggered. However, the memory consumption of this operation seems to be too much. When we did the...

Hi @lafrech thanks for submitting the issue. We believe it was just a intermittent issue with the telemetry server. However, we should make the telemetry reporting component more error tolerant.

@scop thanks a lot for this contribution. Can you please check the CLA as mentioned above?

I get the same issue. Any updates?