|
Hi, minx was freeze or stop because some transactions showed state "idle
in transaction" continuously, for it to the frequency of vacuum execution has been increased all tables, and this caused minx in the table to be updated and the queries improved a lot and the transactions with state "idle in transaction" did not continue.
Thank you all
Best regards De: Alexis Zapata <alexise23@xxxxxxxxxxx>
Enviado: domingo, 13 de noviembre de 2022 9:50 a. m. Para: Laurenz Albe <laurenz.albe@xxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx <pgsql-general@xxxxxxxxxxxxxxxxxxxx> Asunto: RE: Table : Bloat grow high
Hi Laurenz ,
I found that xmin does not change when running the vacuum.
De: Laurenz Albe <laurenz.albe@xxxxxxxxxxx>
Enviado: sábado, 12 de noviembre de 2022 9:05 a. m. Para: Alexis Zapata <alexise23@xxxxxxxxxxx>; pgsql-general@xxxxxxxxxxxxxxxxxxxx <pgsql-general@xxxxxxxxxxxxxxxxxxxx> Asunto: Re: Table : Bloat grow high On Fri, 2022-11-11 at 17:09 +0000, Alexis Zapata wrote:
> In postgresql 13.5 I have a table (size 3.1 GB) and in this table occurs near to > 200 updates per second, after 2 days the size table is 7 GB and bloat grow to 45% and > the query operations are degraded. vacuum runs every 5 seconds over this. but the > bloat growth continues, to solve the > problem quickly, we have made a replica of the table with a trigger, then a copy > of the data and in a > transaction we rename the table, but it would not be the best solution. > Some suggestion about stop this size increase or parameter to setting up? You'd be most happy with HOT updates. Make sure that there is no index on any of the columns you update, and change the table to have a "fillfactor" less than 100. Then you can get HOT updates which don't require VACUUM for cleaning up. https://www.cybertec-postgresql.com/en/hot-updates-in-postgresql-for-better-performance/ Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com |
