Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size
| От | Aleš Zelený |
|---|---|
| Тема | Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size |
| Дата | |
| Msg-id | CAODqTUbMEuEXVhDhk_kNhbe4Udg2DBnyaN5PorHAwNm_Oj3RLw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: BUG #18573: Analyze command consumes several GB of memory - more than analyzed table size (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
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 |
| Список | pgsql-bugs |
Hello,
the default statistics target is:
powa=# show default_statistics_target ;
default_statistics_target
---------------------------
2500
(1 row)
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
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 по дате отправления: