Re: Postgres Query Plan Live Lock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Pweaver (Paul Weaver)" <pweaver@xxxxxxxxxxx>
Subject: Re: Postgres Query Plan Live Lock
From: bricklen <bricklen@xxxxxxxxx>
Date: Wed, 5 Feb 2014 08:39:45 -0800
Cc: "pgsql-performance@xxxxxxxxxxxxxx list" <pgsql-performance@xxxxxxxxxxxxxx>, Michael Vezza <michael@xxxxxxxxxxx>
In-reply-to: <CAFTGa=mvkpL_mOi4NT4LbB3E1QnqVfQ+QQfgSJBfZ1WHujnvpA@mail.gmail.com>

On Mon, Feb 3, 2014 at 1:35 PM, Pweaver (Paul Weaver) <pweaver@xxxxxxxxxxx> wrote:

table_name stats:
~ 400,000,000 rows
We are deleting 10,000,000s of rows in 100,000 row increments over a few days time prior/during this slowdown.

If you issue "VACUUM" or "VACUUM ANALYZE" after each DELETE, do the SELECTs become more responsive?

References:
- Postgres Query Plan Live Lock
  - From: Pweaver (Paul Weaver)

Prev by Date: Re: increasing query time after analyze
Next by Date: Re: Postgres Query Plan Live Lock
Previous by thread: Re: Postgres Query Plan Live Lock
Next by thread: increasing query time after analyze
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux