On 6/26/24 00:03, Shenavai, Manuel wrote:
Thanks for the suggestions.
I checked pg_locks shows and pg_stat_activity but I could not find a LOCK or
an transaction on this (at this point in time).
I assume that this problem may relate to long running transactions which write
a lot of data. Is t
sage-
> From: Adrian Klaver
> Sent: 22 June 2024 23:17
> To: Shenavai, Manuel ; Achilleas Mantzios <
> a.mantz...@cloud.gatewaynet.com>; pgsql-general@lists.postgresql.org
> Subject: Re: Autovacuum, dead tuples and bloat
>
> On 6/22/24 13:13, Shenavai, Manuel wrote:
>
other things.
>
> Best regards,
> Manuel
>
> -Original Message-
> From: Adrian Klaver
> Sent: 21 June 2024 22:39
> To: Shenavai, Manuel ; Achilleas Mantzios
> ; pgsql-general@lists.postgresql.org
> Subject: Re: Autovacuum, dead tuples and bloat
>
> On 6
laver
Sent: 21 June 2024 22:39
To: Shenavai, Manuel ; Achilleas Mantzios
; pgsql-general@lists.postgresql.org
Subject: Re: Autovacuum, dead tuples and bloat
On 6/21/24 12:31, Shenavai, Manuel wrote:
Hi,
Thanks for the suggestions. I found the following details to our
autovacuum (see below). The
use?
Best regards,
Manuel
-Original Message-
From: Adrian Klaver
Sent: 21 June 2024 22:39
To: Shenavai, Manuel ; Achilleas Mantzios
; pgsql-general@lists.postgresql.org
Subject: Re: Autovacuum, dead tuples and bloat
On 6/21/24 12:31, Shenavai, Manuel wrote:
> Hi,
>
> Thanks for the s
On 6/21/24 12:31, Shenavai, Manuel wrote:
Hi,
Thanks for the suggestions. I found the following details to our
autovacuum (see below). The related toast-table of my table shows some
logs related the vacuum. This toast seems to consume all the data
(27544451 pages * 8kb ≈ 210GB )
Those tuple
"n_tup_hot_upd": 0,
"n_tup_ins": 112635281,
"n_tup_upd": 0,
"relid": "27240",
"relname": "pg_toast_27236",
"schemaname": "pg_toast",
"seq_scan": 0,
"seq_tup_read": 0,
avg read rate: 183.934 MB/s, avg write
rate: 1.597 MB/s
system usage: CPU: user: 1.47 s,
system: 1.43 s, elapsed: 13.24 s",
"processId": 8946,
"sqlerrcode": "0",
Στις 20/6/24 19:46, ο/η Shenavai, Manuel έγραψε:
Hi everyone,
we can see in our database, that the DB is 200GB of size, with 99%
bloat. After vacuum full the DB decreases to 2GB.
DB total size: 200GB
DB bloat: 198 GB
DB non-bloat: 2GB
We further see, that during bulk updates (i.e. a long
On Thu, Jun 20, 2024 at 12:47 PM Shenavai, Manuel
wrote:
> Hi everyone,
>
>
>
> we can see in our database, that the DB is 200GB of size, with 99% bloat.
> After vacuum full the DB decreases to 2GB.
>
> DB total size: 200GB
>
> DB bloat: 198 GB
>
> DB non-bloat: 2GB
>
>
>
> We further see, that d
On 6/20/24 09:46, Shenavai, Manuel wrote:
Hi everyone,
we can see in our database, that the DB is 200GB of size, with 99%
bloat. After vacuum full the DB decreases to 2GB.
DB total size: 200GB
DB bloat: 198 GB >
DB non-bloat: 2GB
We further see, that during bulk updates (i.e. a long running
11 matches
Mail list logo
