Re: [PERFORM] Slow function in queries SELECT clause.

2010-08-12 Thread Davor J.
Tom Lane t...@sss.pgh.pa.us wrote in message news:25116.1277047...@sss.pgh.pa.us... Davor J. dav...@live.com writes: Suppose 2 functions: factor(int,int) and offset(int, int). Suppose a third function: convert(float,int,int) which simply returns $1*factor($2,$3)+offset($2,$3) All three

Re: [PERFORM] Slow function in queries SELECT clause.

2010-06-21 Thread Davor J.
the functions. So, as far as I understand the Postgres workings, this shouldn't pose a problem. Regards, Davor Tom Lane t...@sss.pgh.pa.us wrote in message news:25116.1277047...@sss.pgh.pa.us... Davor J. dav...@live.com writes: Suppose 2 functions: factor(int,int) and offset(int, int). Suppose a third

[PERFORM] Slow function in queries SELECT clause.

2010-06-20 Thread Davor J.
I think I have read what is to be read about queries being prepared in plpgsql functions, but I still can not explain the following, so I thought to post it here: Suppose 2 functions: factor(int,int) and offset(int, int). Suppose a third function: convert(float,int,int) which simply returns

Re: [PERFORM] Slow function in queries SELECT clause.

2010-06-20 Thread Davor J.
) AND (sens_chan_data_timestamp = '2008-06-18 00:00:00'::timestamp without time zone)) Total runtime: 694.968 ms Szymon Guz mabew...@gmail.com wrote in message news:aanlktimb8-0kzrrbddqgxnz5tjdgf2t3ffbu2lvx-...@mail.gmail.com... 2010/6/19 Davor J. dav...@live.com I think I have read what

[PERFORM] queries with subquery constraints on partitioned tables not optimized?

2010-02-02 Thread Davor J.
Let's say you have one partitioned table, tbl_p, partitioned according to the PK p_pk. I have made something similar with triggers, basing myself on the manual for making partitioned tables. According to the manual, optimizer searches the CHECKs of the partitions to determine which table(s) to