| From: | Esteban Zimanyi <ezimanyi(at)ulb(dot)ac(dot)be> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: How to disable the autovacuum ? |
| Date: | 2021-05-31 14:10:41 |
| Message-ID: | CAPqRbE5PcOyz=Cadq+9k+C-pKXtKPY+kLs3SouRktSYKt+=K6A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Many thanks Tom for your feedback. I appreciate it.
Actually the tests work in parallel with autovacuum, I just wanted to
minimize the test time since the autovacuum launches in the middle of the
many regression and robustness tests. But then I follow your advice.
Regards
Esteban
On Mon, May 31, 2021 at 3:49 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Esteban Zimanyi <ezimanyi(at)ulb(dot)ac(dot)be> writes:
> > Any idea how to disable the autovacuum during the regression and coverage
> > tests for the MobilityDB extension ?
>
> TBH, this seems like a pretty bad idea. If your extension doesn't
> behave stably with autovacuum it's not going to be much use in the
> real world.
>
> In the core tests, we sometimes disable autovac for individual
> tables using a per-table storage option, but that's a last resort.
>
> regards, tom lane
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-05-31 14:16:11 | make world and install-world without docs |
| Previous Message | vignesh C | 2021-05-31 14:10:19 | Re: CREATE COLLATION - check for duplicate options and error out if found one |