| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Marko Tiikkaja <marko(at)joh(dot)to> |
| Cc: | Michal Novotny <michal(dot)novotny(at)trustport(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Question about DROP TABLE |
| Date: | 2016-01-12 11:25:03 |
| Message-ID: | CAFj8pRDQN6pZqWR-2L7e8SEagao0vhCsLpDS4uHyGfhVfT1Y5w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2016-01-12 12:22 GMT+01:00 Marko Tiikkaja <marko(at)joh(dot)to>:
> On 12/01/16 12:17, Pavel Stehule wrote:
>
>> 2016-01-12 12:14 GMT+01:00 Michal Novotny <michal(dot)novotny(at)trustport(dot)com>:
>>
>> Hi Pavel,
>>> thanks for the information. I've been doing more investigation of this
>>> issue and there's autovacuum running on the table however it's
>>> automatically starting even if there is "autovacuum = off" in the
>>> postgresql.conf configuration file.
>>>
>>>
>> Real autovacuum is automatically cancelled. It looks like VACUUM started
>> by
>> cron, maybe?
>>
>
> Not if it's to prevent wraparound, which isn't unlikely if autovacuum=off.
>
I didn't know it.
Thank you
Pavel
>
>
> .m
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2016-01-12 11:26:01 | Re: Optimization for updating foreign tables in Postgres FDW |
| Previous Message | Marko Tiikkaja | 2016-01-12 11:22:17 | Re: Question about DROP TABLE |