s
I am on Windows XP Service pack 2 with PostgreSQL 8.2 beta2
Thanks,
Jean-Pierre Pelletier
e-djuster
---(end of broadcast)---
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
Explain analyze on my 8.0.1 installation does report the time for
slower queries but for this small query it reports 0.000 ms
- Original Message -
From: "Josh Berkus"
To:
Cc: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>; "John Arbash
Meinel"
Thanks everybody for your help, I'll be awaiting the fix.
I've also noticed that pg_stat_activity is always empty even if
stats_start_collector = on
- Original Message -
From: "Michael Fuhr" <[EMAIL PROTECTED]>
To: "Jean-Pierre Pelletier"
my settings are:
effective_cache_size = 1000
random_page_cost = 4
work_mem = 2
- Original Message -
From: "Josh Berkus"
To: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
Sent: Thursday, September 22, 2005 6:58 PM
Subject: Re: [PERFORM] Queries 15 times sl
I don't know if it makes a difference but in my tables,
content.supplierid and content.priceid were nullable.
- Original Message -
From: "Michael Fuhr" <[EMAIL PROTECTED]>
To: "Josh Berkus"
Cc: ; "Jean-Pierre Pelletier"
<[EMAIL PROTECT
- Original Message -
From: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 22, 2005 6:37 PM
Subject: Re: [PERFORM] Queries 15 times slower on 8.1 beta 2 than on 8.0
How do I produce an "Index scan plan" ?
- Original Message
; on price p (cost=0.00..1606505.44
rows=58147
5 width=4) (actual time=0.008..370.854 rows=164842 loops=1)
Total runtime: 729.192 ms
- Original Message -
From: "John Arbash Meinel" <[EMAIL PROTECTED]>
To: "Jean-Pierre Pelletier" <[EMAIL PROTECTED]>
Cc:
ot;.supplierid = s.supplierid)"
" -> Index Scan using "Price Id" on price p (cost=0.00..5.53 rows=1
width=4) (actual time=0.000..0.000 rows=1 loops=1)"
"Index Cond: ("outer".priceid = p.priceid)"
"Total runtime
All indexes are there, and I've analyzed the three
tables.
I turned off seq scan, the query plans became
identical but the performance
was not better.
- Original Message -
From:
Gavin M. Roy
To: Jean-Pierre Pelletier
Cc: pgsql-performance@postgresql.org
Any ideas why it's slower?
Thanks
Jean-Pierre Pelletier
e-djuster
==
create table Price (
PriceId INTEGER NOT NULL DEFAULT NEXTVAL('PriceId'),
ItemIdINTEGER NOT NULL,
SupplierI
10 matches
Mail list logo