From: Tom Lane <tgl@sss.pgh.pa.us>
To: 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: Wed, 07 Aug 2024 10:46:06 -0400
Message-ID: <1959772.1723041966@sss.pgh.pa.us> (raw)
In-Reply-To: <18573-4bd97c0c25e99339@postgresql.org>
References: <18573-4bd97c0c25e99339@postgresql.org>
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
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: <1959772.1723041966@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