Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
Date
Msg-id 2223506.1723127786@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size  (Aleš Zelený <zeleny.ales@gmail.com>)
List pgsql-bugs
=?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= <zeleny.ales@gmail.com> writes:
> the default statistics target is:
>  2500

> So I've changed it to the default:
> powa=# ALTER TABLE testcase_t3 ALTER COLUMN records SET STATISTICS 100;

> The memory consumption drops down to ~ 1.1GB
> So you were right, thanks!

Yeah, the array statistics collection code is a bit of a memory hog
compared to most other data types.  I'm not sure that's a bug exactly;
there are more kinds of stats that we want to collect for arrays, such
as per-element stats.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Tender Wang
Date:
Subject: Re: BUG #18541: Reattaching a partition referenced by a foreign key fails with an error
Next
From: PG Bug reporting form
Date:
Subject: BUG #18578: Broken postgresql12-*-12.20-1 rpms