| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| 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:20:32 |
| Message-ID: | 20160112112032.vecda6d7fjdomnt7@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-01-12 12:17:09 +0100, 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?
Unless it's an anti-wraparound autovacuum...
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Tiikkaja | 2016-01-12 11:22:17 | Re: Question about DROP TABLE |
| Previous Message | Anastasia Lubennikova | 2016-01-12 11:19:26 | Re: WIP: Covering + unique indexes. |