From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Ciano Saraiva <saraiva(dot)ufc(at)gmail(dot)com> |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: Suggestions on postgres |
Date: | 2015-04-30 16:02:14 |
Message-ID: | CAKFQuwbBPze5FiGm0f2jWqgeBf-+nkCk3FL+bdaYeMprXddHZQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Apr 30, 2015 at 6:20 AM, Ciano Saraiva <saraiva(dot)ufc(at)gmail(dot)com>
wrote:
> Hello Postgres team,
>
> Wanted to give a suggestion in relation to [set enable_seqscan = off]
> command, the problem is that even disabled the SGBD can still use the
> sequential search depending on the query, my suggestion is that invez this
> command, it would be more intuitive even for IHC issues it was a command
> type [set enable_indexscan = ON ], this command does not sequential would
> disable the search, but would enable the search using indixes, it is clear
> that the SGBD that would decide which search would be better to use (
> sequential search and search using indexes). Because the command that is
> currently (set enable_seqscan = off) makes the user think it will turn off once
> and for all the sequential searches, but that's not what happens that he can
> still use.
>
>
I don't see anything about these so-called planner hints changing no
matter how potentially confusing they may be.
They are documented (and easily searched for) here:
http://www.postgresql.org/docs/9.4/static/runtime-config-query.html
and the point you are making is explicitly explained in the comment about
enable_seqscan.
David J.
P.S. What are "SGDB", "IHC issues" and "invez"?
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2015-04-30 16:06:45 | Re: Failure to coerce unknown type to specific type |
Previous Message | Andres Freund | 2015-04-30 14:53:21 | Re: [SPAM] BUG #13143: Cannot stop and restart a streaming server with a replication slot |