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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Plan changes from index scan to seq scan after 5 executions
Date: 2017-09-30 18:03:32
Message-ID: CAKFQuwbHQ1DGqcOW9YmZ7OJNYOR+H6c9VePVuu84-bS7Joqhaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sat, Sep 30, 2017 at 10:57 AM, Alexander Kukushkin <cyberdemn(at)gmail(dot)com>
wrote:

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

Please provide the output of:

SELECT version();

David J.
​

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alexander Kukushkin 2017-09-30 18:15:35 Re: Plan changes from index scan to seq scan after 5 executions
Previous Message Alexander Kukushkin 2017-09-30 17:57:29 Plan changes from index scan to seq scan after 5 executions