Kevin Grittner wrote:
Thomas Zaksek wrote:
Is this query plan near to optimal or are their any serious flaws?
I didn't see any problem with the query, but with the information
provided, we can't really tell if you need to reconfigure something,
or maybe add an index.
The plan gen
Hi Thomas,
How is 'messungen_v_dat_2009_04_13_gtyp_minute_tag_idx' defined? What is
the row count for the table?
Mike
Hi,
subject is the following type of query needed in a function to select
data:
SELECT ' 13.04.2009 12:00:00 ' AS zeit,
Thomas Zaksek wrote:
> Is this query plan near to optimal or are their any serious flaws?
I didn't see any problem with the query, but with the information
provided, we can't really tell if you need to reconfigure something,
or maybe add an index.
The plan generated for the query is doing a
On Mon, 27 Jul 2009, Thomas Zaksek wrote:
Nested Loop (cost=0.00..66344.47 rows=4750 width=10)
(actual time=134.160..19574.228 rows=4148 loops=1)
-> Index Scan using messungen_v_dat_2009_04_13_gtyp_minute_tag_idx on
messungen_v_dat_2009_04_13 m
(cost=0.00..10749.14 r
Hello
maybe is wrong tip, but your function like de* should be slow. What is
time of query without calling these functions?
Pavel Stehule
2009/7/27 Thomas Zaksek :
> Hi,
> subject is the following type of query needed in a function to select data:
>
> SELECT ' 13.04.2009 12:00:00 ' AS zeit,
>
>
Hi,
subject is the following type of query needed in a function to select data:
SELECT ' 13.04.2009 12:00:00 ' AS zeit,
'M' AS ganglinientyp
