From: Tom Lane <tgl@sss.pgh.pa.us>
To: Aleš Zelený <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
Date: Thu, 08 Aug 2024 10:36:26 -0400
Message-ID: <2223506.1723127786@sss.pgh.pa.us> (raw)
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>
=?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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, zeleny.ales@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
In-Reply-To: <2223506.1723127786@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox