Re: Large tables, ORDER BY and sequence/index scans - Mailing list pgsql-general

From Milan Zamazal
Subject Re: Large tables, ORDER BY and sequence/index scans
Date
Msg-id 87skak2u77.fsf@blackbird.nest.zamazal.org
Whole thread Raw
In response to Re: Large tables, ORDER BY and sequence/index scans  (John R Pierce <pierce@hogranch.com>)
List pgsql-general
>>>>> "JRP" == John R Pierce <pierce@hogranch.com> writes:

    >> effective_cache_size = 128MB

    JRP> thats rather small unless your systme is very memory
    JRP> constrained.  assuming postgres is the primary disk IO consumer
    JRP> on this ysstem, take a look at the cached' value on TOP or
    JRP> whatever after its been running, thats a good first order
    JRP> estimate of effective_cache_size.... this is often half or more
    JRP> of your physical memory.

Indeed, increasing effective_cache_size helps, thanks.

Thank you all for the tips, I hope I understand the planner behavior for
my queries better now.

Regards,
Milan Zamazal


pgsql-general by date:

Previous
From: Guillaume Lelarge
Date:
Subject: Re: reason for default PGSTAT_ACTIVITY_SIZE
Next
From: Tim Uckun
Date:
Subject: Re: timestams in the the pg_standby output