Re: Temporarily very slow planning time after a big delete

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: walter(at)carezone(dot)com
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Temporarily very slow planning time after a big delete
Date: 2019-05-21 02:15:09
Message-ID: CAKJS1f_XKnknLkv5s2cYxpoJ8KAJf0aL2ELK3uYTsiZ2VcNTZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, 21 May 2019 at 14:04, Walter Smith <walter(at)carezone(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mariel Cherkassky 2019-05-21 09:01:31 Re: Trying to handle db corruption 9.6
Previous Message Walter Smith 2019-05-21 02:12:05 Re: Temporarily very slow planning time after a big delete