Re: [PERFORM] Bad plan for nested loop + limit

On Sun, Feb 15, 2009 at 5:29 AM, David Wilson wrote: > On Sat, Feb 14, 2009 at 5:25 PM, Alexander Staubo wrote: >> >> Output from "explain analyze": >> >> Limit (cost=0.00..973.63 rows=4 width=48) (actual >> time=61.554..4039.704 rows=1 loops=1) >> -> Nested Loop (cost=0.00..70101.65 rows=2

Re: [PERFORM] I/O increase after upgrading to 8.3.5

On Sat, 14 Feb 2009, Alexander Staubo wrote: Are there any statistics, either in PostgreSQL proper or in the OS, that I can use as metrics to guide the tuning? For example, is there anything in pg_stat_bgwriter that can help me tune the bgwriter_lru_* settings? http://www.westnet.com/~gsmith/

Re: [PERFORM] I/O increase after upgrading to 8.3.5

On Sat, 14 Feb 2009, Alexander Staubo wrote: Is there any statistic available that can tell me whether work_mem is being exceeded? As of 8.3, log_temp_files puts information about them into your logs; see http://www.postgresql.org/docs/current/static/runtime-config-logging.html -- * Greg Sm