Re: [PERFORM] "append" takes a lot of time in a query

2008-05-09 Thread Tom Lane
Frank Dekervel <[EMAIL PROTECTED]> writes: > this turns this query in an append of a whole lot of seq scan/ index scan's. > These scans are predictably quick, but the "append" takes 5 seconds (and the > numbers of the scans do not add up to the append actual time) It says 5 milliseconds, not 5 s

[PERFORM] "append" takes a lot of time in a query

2008-05-09 Thread Frank Dekervel
Hello, I have a strange performance problem with postgresql 8.3 (shipped with ubuntu hardy) and a query that seems very simple: explain analyze SELECT * FROM (part LEFT OUTER JOIN part_lang ON part.id = part_lang.id) WHERE part.parent = 49110; query plan here: http://front7

Re: [PERFORM] multiple joins + Order by + LIMIT query performance issue

2008-05-09 Thread Scott Marlowe
On Fri, May 9, 2008 at 1:18 AM, Antoine Baudoux <[EMAIL PROTECTED]> wrote: > Ok, I've tried everything, and the planner keeps choosing index scans when > it shouldnt. > > Is there a way to disable index scans? You can use "set enable_indexscan off;" as the first command I've had one or two repor

Re: [PERFORM] multiple joins + Order by + LIMIT query performance issue

2008-05-09 Thread Antoine Baudoux
Ok, I've tried everything, and the planner keeps choosing index scans when it shouldnt. Is there a way to disable index scans? Antoine -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-