From: | Ciano Saraiva <saraiva(dot)ufc(at)gmail(dot)com> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Suggestions on postgres |
Date: | 2015-04-30 13:20:53 |
Message-ID: | CAFKbJiUdk3zFky_CZL8eJn=vV3W-CQ4P8D3CU4EkJ_Mp1UEHwA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
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.
Att, Ciano Saraiva.
From | Date | Subject | |
---|---|---|---|
Next Message | Patrice Drolet | 2015-04-30 13:48:52 | Re: [SPAM] BUG #13143: Cannot stop and restart a streaming server with a replication slot |
Previous Message | Michael Paquier | 2015-04-30 13:08:39 | Re: Re: [BUGS] BUG #11805: Missing SetServiceStatus call during service shutdown in pg_ctl (Windows only) |