pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Laurent Raufaste <analogue@glop.org>
To: pgsql-performance@postgresql.org
Subject: Re: PG planning randomly ?
Date: Tue, 26 Feb 2008 16:35:03 +0100
Message-ID: <669dc9710802260735y2fb72ec9l2aa70c12c6636ea0@mail.gmail.com> (raw)
In-Reply-To: <669dc9710802260719h61d846b3hd50b7f547bcb82c3@mail.gmail.com>
References: <669dc9710802260719h61d846b3hd50b7f547bcb82c3@mail.gmail.com>

2008/2/26, Laurent Raufaste <analogue@glop.org>:
> Hi,
>
>  I'm having some issues with this simple query:
>
>  SELECT
>   _comment.*,
>   _article.title AS article_title,
>   _article.reference AS article_reference
>  FROM
>   _comment
>   INNER JOIN _article
>     ON _article.id = _comment.parent_id
>  WHERE
>   _comment.path <@ '0.1.3557034'
>  ORDER BY
>   _comment.date_publishing DESC
>  OFFSET 0
>  LIMIT 5
>  ;

I forgot the table definition, here it is ;)

                                              Table "ob2._comment"
      Column       |            Type             |
     Modifiers
-------------------+-----------------------------+--------------------------------------------------------------
 id                | bigint                      | not null default
nextval('element_id_sequence'::regclass)
 parent_id         | bigint                      |
 path              | ltree                       |
 data              | text                        |
 date_creation     | timestamp without time zone | not null default now()
 date_publishing   | timestamp without time zone | not null default now()
 date_modification | timestamp without time zone | not null default now()
 counters          | hstore                      |
 reference         | integer                     | not null default
nextval('_comment_reference_seq'::regclass)
 text              | text                        |
Indexes:
    "_comment_pkey" PRIMARY KEY, btree (id), tablespace "indexspace"
    "gist_idx_comment_path" gist (path), tablespace "indexspace"
    "idx_comment_date_creation" btree (date_creation), tablespace "indexspace"
    "idx_comment_date_publishing" btree (date_publishing), tablespace
"indexspace"
    "idx_comment_parent_id" btree (parent_id), tablespace "indexspace"
    "idx_comment_reference" btree (reference), tablespace "indexspace"
Inherits: _element

Thanks for looking into ou problem !

-- 
Laurent Raufaste
<http://www.glop.org/;



view thread (12+ messages)  latest in thread

Message-ID: <669dc9710802260735y2fb72ec9l2aa70c12c6636ea0@mail.gmail.com>
Permalink:  ../669dc9710802260735y2fb72ec9l2aa70c12c6636ea0@mail.gmail.com/
Also on:    postgresql.org/message-id/669dc9710802260735y2fb72ec9l2aa70c12c6636ea0@mail.gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: analogue@glop.org
  Subject: Re: PG planning randomly ?
  In-Reply-To: <669dc9710802260735y2fb72ec9l2aa70c12c6636ea0@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox