| From: | rihad <rihad(at)mail(dot)ru> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| 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 15:44:04 |
| Message-ID: | c7d435c1-a6f6-d570-1698-b8791161d406@mail.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 04/11/2019 07:40 PM, Jeff Janes wrote:
> On Thu, Apr 11, 2019 at 10:28 AM rihad <rihad(at)mail(dot)ru
> <mailto:rihad(at)mail(dot)ru>> wrote:
>
>
> 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.
>
>
> The disk usage doesn't reach a steady state after one or two
> autovacs? Or it does, but you are just unhappy about the ratio
> between the steady state size and the theoretical fully packed size?
>
> Cheers,
>
> Jeff
Since we dump&restore production DB daily into staging environment, the
difference in size (as reported by psql's \l+) is 11GB in a freshly
restored DB as opposed to 70GB in production.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2019-04-11 15:54:30 | Re: When do vacuumed pages/tuples become available for reuse? |
| Previous Message | Jeff Janes | 2019-04-11 15:40:54 | Re: When do vacuumed pages/tuples become available for reuse? |