Re: [GENERAL] 7.3 Prepared statements

I saw this on the GENERAL list and this answer got me thinking.

Do JDBC Prepared statements get the same saved execution plan support?

We currently use PreparedStatements in our framework for JDBC access. We
currently do not retain the PreparedStatement between uses, but if
PostreSQL caches the execution plan, we may need to change our design.

Thanks,

Charlie

Bruce Momjian wrote:

>A view is just syntaxic sugar added to a query that references the view.
>A preparted statement actually saves the execution plan for repeated
>execution.
>
>---------------------------------------------------------------------------
>
>Francisco J Reyes wrote:
>
>
>>On 17 Dec 2002, Neil Conway wrote:
>>
>>
>>
>>>On Tue, 2002-12-17 at 10:19, Ericson Smith wrote:
>>>
>>>
>>>>1. What is the lifetime of the plan created?
>>>>
>>>>
>>>>From the PREPARE reference page:
>>>
>>>Prepared queries are stored locally (in the current backend), and only
>>>exist for the duration of the current database session.
>>>
>>>
>>What is the difference/advantage between a prepared query and a view?
>>
>>
>>---------------------------(end of broadcast)---------------------------
>>TIP 4: Don't 'kill -9' the postmaster
>>
>>
>>
>
>
>

--

Charles H. Woloszynski

ClearMetrix, Inc.
115 Research Drive
Bethlehem, PA 18015

tel: 610-419-2210 x400
fax: 240-371-3256
web: www.clearmetrix.com