From: Radoulov, Dimitre <cichomitiko@gmail.com>
To: MichaelDBA <MichaelDBA@sqlexec.com>
Cc: pgsql-admin@lists.postgresql.org, Julien Rouhaud <rjuju123@gmail.com>
Subject: Re: Temp files for simple queries
Date: Tue, 22 Jun 2021 14:16:31 +0200
Message-ID: <2a8094c3-e2ea-b2cb-59d5-c8a31f1cbe67@gmail.com> (raw)
In-Reply-To: <6fab4381-4a47-0b99-43a9-1ff1c97efd39@sqlexec.com>
References: <45cc44dd-b830-5df5-1f09-171e9874bbc0@gmail.com>
<16aa733d-bcaf-0aa6-f3f0-5206de695e92@gmail.com>
<20210622115506.o2u4u5krplxxc54k@nol>
<6fab4381-4a47-0b99-43a9-1ff1c97efd39@sqlexec.com>
Hello Michael,
On 22/06/2021 14.00, MichaelDBA wrote:
> I'm wondering if bloat could be causing a problem. Perhaps more
> blocks are written to disk including a lot of blocks with little or no
> data due to bloat.
>
Using the query suggested here:
www.citusdata.com/blog/2017/10/20/monitoring-your-bloat-in-postgres/, I
get the following:
databasename | db1
schemaname | schema1
tablename | t1
can_estimate | t
est_rows | 160
pct_bloat | 18
mb_bloat | 0.06
table_mb | 0.352
So the bloat doesn't seem significant.
Best regards
Dimitre
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-admin@postgresql.org
Cc: cichomitiko@gmail.com, MichaelDBA@sqlexec.com, rjuju123@gmail.com
Subject: Re: Temp files for simple queries
In-Reply-To: <2a8094c3-e2ea-b2cb-59d5-c8a31f1cbe67@gmail.com>
* 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