Skip to content

P
Postgres FD Implementation
Commit 17c371fe authored by Tom Lane's avatar Tom Lane
Browse files
Options

Remove unhelpful/misleading advice about how to use SPI_saveplan(). 

Per gripe from Jack Orenstein.
parent 5e08e496
Show whitespace changes
Inline Side-by-side
Showing with 2 additions and 5 deletions
doc/src/sgml/spi.sgml
View file @ 17c371fe
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.47 2006/08/27 23:47:57 tgl Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.48 2006/09/10 20:56:42 tgl Exp $ -->
<chapter id="spi"> <chapter id="spi">
<title>Server Programming Interface</title> <title>Server Programming Interface</title>
...@@ -1614,10 +1614,7 @@ void * SPI_saveplan(void * <parameter>plan</parameter>) ...@@ -1614,10 +1614,7 @@ void * SPI_saveplan(void * <parameter>plan</parameter>)
by <function>SPI_finish</function> and by the transaction manager by <function>SPI_finish</function> and by the transaction manager
and returns a pointer to the saved plan. This gives you the and returns a pointer to the saved plan. This gives you the
ability to reuse prepared plans in the subsequent invocations of ability to reuse prepared plans in the subsequent invocations of
your procedure in the current session. You may save the pointer your procedure in the current session.
returned in a local variable. Always check if this pointer is
<symbol>NULL</symbol> or not either when preparing a plan or using
an already prepared plan in <function>SPI_execute_plan</function>.
</para> </para>
</refsect1> </refsect1>
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment