Re: PostgreSQL does CAST implicitely between int andadomain derived from int - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: PostgreSQL does CAST implicitely between int andadomain derived from int
Date
Msg-id 4A96575C020000250002A3F9@gw.wicourts.gov
Whole thread Raw
In response to Re: PostgreSQL does CAST implicitely between int and adomain derived from int  (Jean-Michel Pouré <jm@poure.com>)
Responses Re: PostgreSQL does CAST implicitely between int andadomain derived from int
List pgsql-performance
Jean-Michel Pouré<jm@poure.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

pgsql-performance by date:

Previous
From: Jean-Michel Pouré
Date:
Subject: Re: PostgreSQL does CAST implicitely between int and adomain derived from int
Next
From: Jean-Michel Pouré
Date:
Subject: Re: PostgreSQL does CAST implicitely between int andadomain derived from int