Re: We should stop telling users to "vacuum that database in single-user mode"

On Wed, 3 Mar 2021 at 01:12, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
> On Tue, Mar 2, 2021 at 7:52 AM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> > I have seen it happen that an instance has a vacuum_cost_limit set and
> > someone did start the database in single-user mode, per the advice of
> > the error message only to find that the VACUUM took a very long time
> > due to the restrictive cost limit. I struggle to imagine why anyone
> > wouldn't want the vacuum to run as quickly as possible in that
> > situation.
>
> Multiple instances running on the same hardware and only one of them
> being in trouble?

You might be right. I'm not saying it's a great idea but thought it
was worth considering.

We could turn to POLA and ask; what would you be more surprised at; 1)
Your database suddenly using more I/O than it had been previously, or;
2) Your database no longer accepting DML.

David