Re: PostgreSQL does CAST implicitely between int andadomain derived from int

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <pgsql-performance(at)postgresql(dot)org>, Jean-Michel Pouré <jm(at)poure(dot)com>
Subject: Re: PostgreSQL does CAST implicitely between int andadomain derived from int
Date: 2009-08-27 14:52:28
Message-ID: 4A96575C020000250002A3F9@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jean-Michel Pouré<jm(at)poure(dot)com> wrote:

> ... Index Cond: ((tid)::integer = 3)

> ... Index Cond: ((n.vid)::integer = (tn.vid)::integer)

> ... Index Cond: ((ncs.nid)::integer = n.nid)

> Total runtime: 0.092 ms

Sorry, but I just had to point that out.
I feel much better now. ;-)

> Does it mean my index is broken and should be rebuilt?

No, probably not.

Just to get another data point, what happens if you run the same query
without taking the index out of the picture, but without the LIMIT or
OFFSET clauses? An EXPLAIN ANALYZE of that would help understand it
more fully.

-Kevin

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Jean-Michel Pouré 2009-08-27 15:10:22 Re: PostgreSQL does CAST implicitely between int andadomain derived from int
Previous Message Jean-Michel Pouré 2009-08-27 14:37:42 Re: PostgreSQL does CAST implicitely between int and adomain derived from int