On Sun, 2022-11-13 at 14:50 +, Alexis Zapata wrote:
> I found that xmin does not change when running the vacuum.
Which xmin?
Yours,
Laurenz Albe
Hi Laurenz ,
I found that xmin does not change when running the vacuum.
De: Laurenz Albe
Enviado: sábado, 12 de noviembre de 2022 9:05 a. m.
Para: Alexis Zapata ; pgsql-general@lists.postgresql.org
Asunto: Re: Table : Bloat grow high
On Fri, 2022-11-11 at 17
On 2022-11-12 08:24:23 -0600, Ron wrote:
> On 11/12/22 08:05, Laurenz Albe wrote:
> 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 update
On 11/12/22 08:05, Laurenz Albe wrote:
On Fri, 2022-11-11 at 17:09 +, 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 degrad
On Fri, 2022-11-11 at 17:09 +, 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
On 11/11/22 11:09, Alexis Zapata wrote:
Hi all,
In postgresql 13.5
Upgrade to at least 13.8. (13.9 was released yesterday.)
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 operation
