Re: Temporarily very slow planning time after a big delete - Mailing list pgsql-performance

From David Rowley
Subject Re: Temporarily very slow planning time after a big delete
Date
Msg-id CAKJS1f_XKnknLkv5s2cYxpoJ8KAJf0aL2ELK3uYTsiZ2VcNTZg@mail.gmail.com
Whole thread Raw
In response to Re: Temporarily very slow planning time after a big delete  (Walter Smith <walter@carezone.com>)
Responses Re: Temporarily very slow planning time after a big delete
List pgsql-performance
On Tue, 21 May 2019 at 14:04, Walter Smith <walter@carezone.com> wrote:
> I'm so sorry -- I meant to give the version, of course. It's 9.6.13.

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3ca930fc3
has been applied since then.

It would be good if you could confirm the problem is resolved after a
vacuum.  Maybe run VACUUM VERBOSE on the table and double check
there's not some large amount of tuples that are "nonremovable".

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-performance by date:

Previous
From: Walter Smith
Date:
Subject: Re: Temporarily very slow planning time after a big delete
Next
From: Mariel Cherkassky
Date:
Subject: Re: Trying to handle db corruption 9.6