Thanks for that, that was exactly the issue.
It absolutely is IMMUTABLE and changing it from VOLATILE has fixed the issue.
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: 26 July 2012 16:52
To: Russell Keane
Subject: Re: [SQL] FW: view derived from view doesn't use indexes
Russell Keane <Russell(dot)Keane(at)inps(dot)co(dot)uk> writes:
> Using PG 9.0 and given the following definitions:
> CREATE OR REPLACE FUNCTION status_to_flag(status character) RETURNS
> integer AS $BODY$ ...
> LANGUAGE plpgsql
> CREATE OR REPLACE VIEW test_view1 AS
> SELECT status_to_flag(test_table.status) AS flag, test_table.code_id
> FROM test_table;
> CREATE OR REPLACE VIEW test_view2 AS
> SELECT *
> FROM test_view1
> WHERE test_view1.flag = 1;
I think the reason why the planner is afraid to flatten this is that the function is (by default) marked VOLATILE. Volatile functions in the select list are an optimization fence. That particular function looks like it should be IMMUTABLE instead, since it depends on no database state. If it does look at database state, you can probably use STABLE.
regards, tom lane
In response to
pgsql-sql by date
|Next:||From: Andreas||Date: 2012-07-28 01:57:00|
|Subject: join against a function-result fails|
|Previous:||From: Tom Lane||Date: 2012-07-26 15:51:40|
|Subject: Re: FW: view derived from view doesn't use indexes|