From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | rihad <rihad(at)mail(dot)ru> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: When do vacuumed pages/tuples become available for reuse? |
Date: | 2019-04-11 14:41:10 |
Message-ID: | 20190411144110.GA27020@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2019-Apr-11, rihad wrote:
> On 04/11/2019 06:20 PM, Tom Lane wrote:
> > rihad <rihad(at)mail(dot)ru> writes:
> > > Thanks! Our autovacuum_work_mem = 1GB, so this probably means any space
> > > would be available for reuse only at the end of the vacuum?
> > It's six bytes per dead tuple, last I checked ... you do the math.
> >
> > > Are there
> > > any downsides in decreasing it to, say, 64MB? I see only pluses )
> > Well, usually people prefer to minimize the number of passes over
> > the indexes.
> Yup, it's just that n_dead_tuples grows by several hundred thousand (the
> table sees much much more updates than inserts) and disk usage grows
> constantly between several hour long vacuum runs. Running vacuum full isn't
> an option.
Perhaps it'd be better to vacuum this table much more often.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | rihad | 2019-04-11 14:43:17 | Re: When do vacuumed pages/tuples become available for reuse? |
Previous Message | rihad | 2019-04-11 14:27:52 | Re: When do vacuumed pages/tuples become available for reuse? |