Hi, Mario,
Mario Splivalo wrote:
>>> Is postgres going to make one query plan, or each view has it own
>>> query
>>> plan?
>> Have you taken a look at the EXPLAIN ANALYZE output of the queries?
>> You can see exactly which plan PostgreSQL will use.
>
> So, the performance will be the same if
On Fri, 2006-06-30 at 21:47 +0900, Michael Glaesemann wrote:
> On Jun 30, 2006, at 21:35 , Mario Splivalo wrote:
>
> > Is postgres going to make one query plan, or each view has it own
> > query
> > plan?
>
> Have you taken a look at the EXPLAIN ANALYZE output of the queries?
> You can see ex
On Jun 30, 2006, at 21:35 , Mario Splivalo wrote:
Is postgres going to make one query plan, or each view has it own
query
plan?
Have you taken a look at the EXPLAIN ANALYZE output of the queries?
You can see exactly which plan PostgreSQL will use.
Michael Glaesemann
grzm seespotcode net
Let's say I have a view like this:
CREATE VIEW v_small AS
SELECT c1, c2
FROM t1 JOIN t2 ON t1.c1 = t2.c2
and then I have another view
CREATE VIEW v_big AS
SELECT c1 FROM v_small WHERE c2 > 5
Now, when I do this:
SELECT * FROM v_big WHERE c1 < 1500
Is postgres going to make one query plan, or
