index2.
Planner tends to choose a plan which has small startup cost when you are
trying to LIMIT a small portion of data over a large data set. It seems that
the following issue also comes from the same root.
http://archives.postgresql.org/pgsql-performance/2007-11/msg00395.php
Best Regards
Galy
Jim C. Nasby wrote:
On Wed, Jan 24, 2007 at 02:37:44PM +0900, Galy Lee wrote:
1. How do we know if autovacuum is enough for my application, or should
I setup a vacuum manually from cron for my application?
Generally I trust autovac unless there's some tables where it's cri
Just have one example here:
workload: run pgbench in 365x24x7
database size: 100GB
the workload distribution:
06:00-24:00 100tps
00:00-06:00 20tps
how should we plan vacuum for this situation to get the highest performance?
Best regards
Galy
Galy Lee wrote:
> Hi,
>
>
the parameters for
vacuum have not been set well, it will make the system rather unstable.
So I just wonder if we should setup a section in the manual about the
tips of vacuum, then many users can easily set the vacuum parameters for
their system.
Best Regards
Galy Lee
NTT OSS Center
