Re: PostgreSQL does CAST implicitely between int and a domain derived from int

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jean-Michel Pouré <jm(at)poure(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: PostgreSQL does CAST implicitely between int and a domain derived from int
Date: 2009-08-29 21:45:24
Message-ID: 1941.1251582324@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jean-Michel =?ISO-8859-1?Q?Pour=E9?= <jm(at)poure(dot)com> writes:
> What do you recommend: using normal types and moving constraints in the
> Drupal database? Is PostgreSQL domain broken as it forces casting or is
> this a no-op for performance?

In principle it should be an unnoticeable slowdown. In the past we've
had some issues with the planner failing to recognize possible
optimizations when there was a cast in the way, but I'm not aware of
any such bugs at the moment.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Greg Stark 2009-08-29 21:48:31 Re: PostgreSQL does CAST implicitely between int and a domain derived from int
Previous Message Jean-Michel Pouré 2009-08-29 20:59:46 Re: PostgreSQL does CAST implicitely between int and a domain derived from int