| From: | Artem Tomyuk <admin(at)leboutique(dot)com> |
|---|---|
| To: | Keith <keith(at)keithf4(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: autovacuum: vacuum analyze vs autovacuum: vacuum |
| Date: | 2018-03-27 16:45:32 |
| Message-ID: | CANYYVqJjpndi1n+Py28dg=i1hVjUGezOZYJ7pq7kqb4jhVNm8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ok, thanks for the clarification.
вт, 27 бер. 2018, 18:48 користувач Keith <keith(at)keithf4(dot)com> пише:
>
>
> On Tue, Mar 27, 2018 at 5:04 AM, Artem Tomyuk <admin(at)leboutique(dot)com>
> wrote:
>
>> Hi, Gurus!
>>
>>
>> As i understand from documentation:
>>
>> when the autovacuum: vacuum analyze will be triggered, it will delete
>> dead tuples and than will analyze table
>> but
>> when the autovacuum: vacuum will be triggered it will only mark for
>> deletion dead tubles.
>>
>> Is it valid explanation for postgres 9.4?
>>
>> Thanks
>>
>
>
> I believe that when the ANALYZE portion of autovacuum kicks in, it only
> does the analyze. Which is why it's frequently tuned to run more often than
> the VACUUM portion of autovacuum since it's less of a load.
>
> Keith
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2018-03-27 21:25:03 | Re: AWS Database Migration Errors Post migration |
| Previous Message | Keith | 2018-03-27 15:47:53 | Re: autovacuum: vacuum analyze vs autovacuum: vacuum |