On 12/6/17 09:40, tibor.fo...@gmail.com wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/9.6/static/app-pgdump.html
> Description:
>
> Explanation for njobs.
> "Run the dump in parallel by dumping njobs tables simultaneously"
On Wed, Dec 6, 2017 at 7:37 AM, hmidi slim wrote:
> Hi,
> When I used explain I found that the query planner use a seq scan to
> execute a query on a table containing about 2 millions rows.However I'm
> creating an index.Why does the planner uses seq scan in place of index
> scan?Does the executi
On Wed, Dec 6, 2017 at 9:37 AM, hmidi slim wrote:
> Hi,
> When I used explain I found that the query planner use a seq scan to
> execute a query on a table containing about 2 millions rows.However I'm
> creating an index.Why does the planner uses seq scan in place of index
> scan?Does the executi
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/9.6/static/app-pgdump.html
Description:
Explanation for njobs.
"Run the dump in parallel by dumping njobs tables simultaneously"
The word "tables" is misleading. Suggest removing it.
Hi,
When I used explain I found that the query planner use a seq scan to
execute a query on a table containing about 2 millions rows.However I'm
creating an index.Why does the planner uses seq scan in place of index
scan?Does the execution of index scan is slower with table containing a
huge amount
