https://rhaas.blogspot.com/2012/01/linux-memory-reporting.html?m=1
I think this awesome blog will clear a lot of 'understanding of top' output
in postgresql context of memory growth.
On Sun, 1 Aug 2021 at 20:04, Vijaykumar Jain <
vijaykumarjain.git...@gmail.com> wrote:
>
> On Sun, 1 Aug 2021 at 10:27, Ayub M wrote:
> >
> > Hello, when maintenance_work_mem and autovacuum_work_mem are set, my
> understanding is that the vacuum and autovacuum sessions should be limited
> to use
"David G. Johnston" writes:
> On Saturday, July 31, 2021, Ayub M wrote:
>> But when default_statistics_target is increased to 3000, the session usage
>> is 463mb
> IIUC, the analyze process doesn’t consult maintenance_work_mem. It simply
> creates an array, in memory, to hold the random sample
On Sun, 1 Aug 2021 at 10:27, Ayub M wrote:
>
> Hello, when maintenance_work_mem and autovacuum_work_mem are set, my
understanding is that the vacuum and autovacuum sessions should be limited
to use the memory limits set by these parameters. But I am seeing more
memory being used than these limits
On Saturday, July 31, 2021, Ayub M wrote:
> But when default_statistics_target is increased to 3000, the session usage
> is 463mb
>
IIUC, the analyze process doesn’t consult maintenance_work_mem. It simply
creates an array, in memory, to hold the random sample of rows needed for
computing the r
