On Fri, May 28, 2021, at 7:22 AM, Tom Lane wrote:
> The text column would cause the table to have an associated toast table [1],
> which in turn would have an index. Both of those would be reallocated as
> new files on-disk during TRUNCATE, just like the table proper.
>
> A plausible theory here
I've been seeing what looks like unbounded memory growth (until the OOM killer
kicks in and kills the postgres process) when running a pl/pgsql function that
performs TRUNCATE statements against various temporary tables in a loop. I
think I've been able to come up with some fairly simple reprodu
