| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Claudio Freire <klaussfreire(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Vacuum: allow usage of more than 1GB of work mem |
| Date: | 2016-09-06 18:23:48 |
| Message-ID: | CA+Tgmob6A=hrut0Fg8LHpY8U70jd5fKutiVCPaaMhHF9-T2S+g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 6, 2016 at 2:16 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> What occurs to me is that we can exactly predict how many tuples we
> are going to get when we autovacuum, since we measure that and we know
> what the number is when we trigger it.
>
> So there doesn't need to be any guessing going on at all, nor do we
> need it to be flexible.
No, that's not really true. A lot can change between the time it's
triggered and the time it happens, or even while it's happening.
Somebody can run a gigantic bulk delete just after we start the
VACUUM.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2016-09-06 18:25:10 | Re: Vacuum: allow usage of more than 1GB of work mem |
| Previous Message | Simon Riggs | 2016-09-06 18:16:27 | Re: Vacuum: allow usage of more than 1GB of work mem |