Re: [PERFORM] PostgreSQL does CAST implicitely between int and adomain derived from int

2009-08-27 Thread Jean-Michel Pouré
Le jeudi 27 août 2009 à 09:16 -0500, Kevin Grittner a écrit : > Then you need to use a better tool to run it. Understood, thanks. cms=# set work_mem = '50MB'; SET cms=# set effective_cache_size = '1GB'; SET cms=# begin transaction; BEGIN cms=# drop index node_comment_statistics_node_comment_time

Re: [PERFORM] PostgreSQL does CAST implicitely between int and adomain derived from int

2009-08-27 Thread Kevin Grittner
>Jean-Michel Pouré wrote: > Does not show any result because of ROLLBACK; Then you need to use a better tool to run it. For example, in psql: test=# create table t2 (c1 int not null); CREATE TABLE test=# insert into t2 select * from generate_series(1,1); INSERT 0 1 test=# create uniqu

Re: [PERFORM] PostgreSQL does CAST implicitely between int and adomain derived from int

2009-08-27 Thread Jean-Michel Pouré
Le jeudi 27 août 2009 à 09:01 -0500, Kevin Grittner a écrit : > The type is always put in there so that you can see what it's doing; > it doesn't reflect anything which is actually taking any time. My query plan for the same query is: "Aggregate (cost=12.75..12.76 rows=1 width=0) (actual time=0.

Re: [PERFORM] PostgreSQL does CAST implicitely between int and adomain derived from int

2009-08-27 Thread Kevin Grittner
Jean-Michel Pouré wrote: > Still casting. For about the tenth time on the topic -- YOUR PROBLEM HAS NOTHING WHATSOEVER TO DO WITH CASTING! Let that go so you can look for the real problem. Just as an example, look at this closely: test=# create table t2 (c1 int not null primary key); NOTICE: