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

From Aleš Zelený
Subject Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
Date
Msg-id CAODqTUbMEuEXVhDhk_kNhbe4Udg2DBnyaN5PorHAwNm_Oj3RLw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
List pgsql-bugs
Hello,

the default statistics target is:

powa=# show default_statistics_target ;
 default_statistics_target
---------------------------
 2500
(1 row)

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

The memory consumption drops down to ~ 1.1GB

So you were right, thanks!

I thought it was a bug, but possibly it is only a space for an improvement for adding a potential limit for similar cases.

Kind regards Ales Zeleny

st 7. 8. 2024 v 16:46 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
PG Bug reporting form <noreply@postgresql.org> writes:
> Is there more I can do to identify why analyze uses that much memory?

What have you got default_statistics_target set to?

You might need to decrease the stats target for that composite-array
column.  compute_array_stats is fairly aggressive about how much
data it will try to collect, and I can believe that that'd add up
when the array elements are of a wide composite type.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Tender Wang
Date:
Subject: Re: BUG #18568: BUG: Result wrong when do group by on partition table!
Next
From: "狂奔的蜗牛"
Date:
Subject: 回复: BUG #18568: BUG: Result wrong when do group by on partition table!