Re: [PERFORM] Finding bottleneck

2005-08-08 Thread Merlin Moncure
Kari Lavikka [EMAIL PROTECTED] writes: samples %symbol name 13513390 16.0074 AtEOXact_CatCache That seems quite odd --- I'm not used to seeing that function at the top of a profile. What is the workload being profiled, exactly? He is running a commit_delay of 8. Could

Re: [PERFORM] Why hash join instead of nested loop?

2005-08-08 Thread Rhett Garber
This is postgres 7.4.1 All the rows involved are integers. Thanks, Rhett On 8/5/05, Tom Lane [EMAIL PROTECTED] wrote: Rhett Garber [EMAIL PROTECTED] writes: Hash Join (cost=5.96..7.04 rows=1 width=14) (actual time=10.591..10.609 rows=1 loops=1) Hash Cond: (outer.id = inner.obj2)

Re: [PERFORM] Finding bottleneck

2005-08-08 Thread Tom Lane
Kari Lavikka [EMAIL PROTECTED] writes: Disk configurations looks something like this: sda: data (10 spindles, raid10) sdb: xlog clog (2 spindles, raid1) sdc: os and other stuff That's definitely wrong. Put clog on the data disk. The entire point of giving xlog its own spindle is

Re: [PERFORM] Why hash join instead of nested loop?

2005-08-08 Thread Tom Lane
Rhett Garber [EMAIL PROTECTED] writes: This is postgres 7.4.1 All the rows involved are integers. Hmph. There is something really strange going on here. I tried to duplicate your problem in 7.4.*, thus: regression=# create table rtmessagestate(id int, f1 char(6)); CREATE TABLE regression=#

Re: [PERFORM] Why hash join instead of nested loop?

2005-08-08 Thread Steinar H. Gunderson
On Mon, Aug 08, 2005 at 08:58:26PM -0400, Tom Lane wrote: Hmph. There is something really strange going on here. I tried to duplicate your problem in 7.4.*, thus: PostgreSQL 7.4.7 (Debian sarge): create table and stuff, exactly the same as you regression=# explain analyze select