Search Postgresql Archives

Re: Plan changes from index scan to seq scan after 5 executions

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

Subject: Re: Plan changes from index scan to seq scan after 5 executions
From: "David G. Johnston" <david.g.johnston@xxxxxxxxx>
Date: Sat, 30 Sep 2017 11:03:32 -0700
Cc: "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAFh8B==j37Y0aCkz75vaw9+B4VWNZUyfL44Z6QdZaPR8ibBnTQ@mail.gmail.com>
References: <CAFh8B==j37Y0aCkz75vaw9+B4VWNZUyfL44Z6QdZaPR8ibBnTQ@mail.gmail.com>

On Sat, Sep 30, 2017 at 10:57 AM, Alexander Kukushkin <cyberdemn@xxxxxxxxx> wrote:

Hi,

Recently I've been investigating a strange behavior of one stored procedure.

Please provide the output of:

SELECT version();

David J.

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

Follow-Ups:
- Re: Plan changes from index scan to seq scan after 5 executions
  - From: Alexander Kukushkin

References:
- Plan changes from index scan to seq scan after 5 executions
  - From: Alexander Kukushkin

Prev by Date: Plan changes from index scan to seq scan after 5 executions
Next by Date: Re: Plan changes from index scan to seq scan after 5 executions
Previous by thread: Plan changes from index scan to seq scan after 5 executions
Next by thread: Re: Plan changes from index scan to seq scan after 5 executions
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux