From: Tom Lane <tgl@sss.pgh.pa.us>
To: =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= <zeleny.ales@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18573: Analyze command consumes several GB of memory - more
 than analyzed table size
In-reply-to: 
 <CAODqTUbMEuEXVhDhk_kNhbe4Udg2DBnyaN5PorHAwNm_Oj3RLw@mail.gmail.com>
References: <18573-4bd97c0c25e99339@postgresql.org>
 <1959772.1723041966@sss.pgh.pa.us>
 <CAODqTUbMEuEXVhDhk_kNhbe4Udg2DBnyaN5PorHAwNm_Oj3RLw@mail.gmail.com>
Comments: In-reply-to =?UTF-8?B?QWxlxaEgWmVsZW7DvQ==?= <zeleny.ales@gmail.com>
	message dated "Thu, 08 Aug 2024 10:31:38 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2223505.1723127786.1@sss.pgh.pa.us>
Date: Thu, 08 Aug 2024 10:36:26 -0400
Message-ID: <2223506.1723127786@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2223506.1723127786%40sss.pgh.pa.us>
Precedence: bulk

=?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