On Tue, Sep 23, 2008 at 3:57 PM, Richard Broersma
<[EMAIL PROTECTED]> wrote:
> SELECT A."dimension_book"."call", SUM( B."dimension_book"."call" ) AS
> OrderedRowNbr
> FROM ( your_above_query_without_the_limits ) AS A
> INNER JOIN ( your_above_query_without_the_limits ) AS B
> ON A."dimension_book".
On Tue, Sep 23, 2008 at 3:25 PM, Colin Copeland <[EMAIL PROTECTED]> wrote:
>>> dimension=# EXPLAIN ANALYZE
>>> SELECT DISTINCT ON ("dimension_book"."call")
>>> "dimension_book"."title"
>>> FROM "dimension_book"
>>> INNER JOIN "dimension_library_books"
>>> ON ("dimension_b
On Sep 23, 2008, at 6:07 PM, Richard Broersma wrote:
On Tue, Sep 23, 2008 at 2:22 PM, Colin Copeland <[EMAIL PROTECTED]
> wrote:
dimension=# EXPLAIN ANALYZE
SELECT DISTINCT ON ("dimension_book"."call")
"dimension_book"."title"
FROM "dimension_book"
INNER JOIN "dimension_lib
On Tue, Sep 23, 2008 at 2:22 PM, Colin Copeland <[EMAIL PROTECTED]> wrote:
> dimension=# EXPLAIN ANALYZE
> SELECT DISTINCT ON ("dimension_book"."call")
> "dimension_book"."title"
> FROM "dimension_book"
> INNER JOIN "dimension_library_books"
> ON ("dimension_book"."i
Hello,
I'm running into performance issues with various queries on a
PostgreSQL database (of books). I'm having trouble understanding the
thinking behind the query planner in this scenario:
http://dpaste.com/hold/80101/
(also attached at bottom of email)
Relation sizes:
dimension_books: 19
