Hello,
I have a big table in the actively working system, in which nothing is
written for a long time, and nothing is read from it. Table size is 15GB
(data only), indexes 150GB.
Since the table does not change, after a while it crosses the
autovacuum_freeze_max_age and an aggressive vacuum is tri
Adrian,
thanks for pointing out the fix. We are just about to update to 11.18 next
month.
Mikhael
On Thu, 16 Feb 2023 at 23:44, Adrian Klaver
wrote:
> On 2/15/23 22:57, Mikhail Balayan wrote:
> > Hello,
> >
> > I have a big table in the actively working system, in which n
>
> >> Even still,
> >> the information about buffers that you've shown does indeed appear to
> >> be total nonsense (while everything else we can see looks plausible).
Actually not only buffers. The elapsed time also looks strange. And this is
the first reason why I paid attention to this situati
makes sense to add information about the
blocking waiting time to the output. Something like:
system usage: CPU: user: 7734.43 s, system: 178.98 s, lock_wait:
1234.56 s, elapsed: 9401.36 s
Mikhail
On Sat, 18 Feb 2023 at 05:35, Peter Geoghegan wrote:
> On Thu, Feb 16, 2023 at 5:40 PM Mikha
0.014348 23 623 fdatasync
0.200.006372 5 1245 kill
0.000.81 5 17 open
0.000.42 412 select
0.000.38 312 close
0.000.00
