Re: I want to make an example of using parameterized path - Mailing list pgsql-general

From Jeff Janes
Subject Re: I want to make an example of using parameterized path
Date
Msg-id CAMkU=1y0fXLrNuvsev989RUiYrQNg4S1xVawwmAAnzC=yaiv_A@mail.gmail.com
Whole thread Raw
In response to I want to make an example of using parameterized path  (高健 <luckyjackgao@gmail.com>)
Responses Re: I want to make an example of using parameterized path  (高健 <luckyjackgao@gmail.com>)
List pgsql-general
On Tue, Jun 18, 2013 at 2:09 AM, 高健 <luckyjackgao@gmail.com> wrote:

 

 postgres=# explain execute s(2);

                                   QUERY PLAN                                    
---------------------------------------------------------------------------------
 Index Only Scan using idx_tst01_id on tst01 t  (cost=0.00..8.38 rows=1 width=4)
   Index Cond: (id < 2)
(2 rows)

postgres=# explain execute s(100000);
                          QUERY PLAN                           
---------------------------------------------------------------
 Seq Scan on tst01 t  (cost=0.00..1693.00 rows=100000 width=4)
   Filter: (id < 100000)
(2 rows)
 
postgres=# 

 

When I just send sql of  " select * from tst01 t where id <2" , it will also produce index only scan plan.

When I just send sql of  " select * from tst01 t where id < 100000", it will also produce seq scan plan.

 

So I think that  the above example can not show that "parameterized path" has been created.


But if you try the PREPAREd sets in versions before 9.2, you will find they use the same plan as each other.  Allowing them to differ based on the parameter they are executed with, just like the non-PREPARE ones differ, is what parameterized paths is all about.

Cheers,

Jeff

pgsql-general by date:

Previous
From: Robert Fitzpatrick
Date:
Subject: Using functions to calc field values in other table
Next
From: bhanu udaya
Date:
Subject: Postgres DB crashing