Skip to content

Commit 17c371f

Browse files
committed
Remove unhelpful/misleading advice about how to use SPI_saveplan().
Per gripe from Jack Orenstein.
1 parent 5e08e49 commit 17c371f

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

doc/src/sgml/spi.sgml

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.47 2006/08/27 23:47:57 tgl Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.48 2006/09/10 20:56:42 tgl Exp $ -->
22

33
<chapter id="spi">
44
<title>Server Programming Interface</title>
@@ -1614,10 +1614,7 @@ void * SPI_saveplan(void * <parameter>plan</parameter>)
16141614
by <function>SPI_finish</function> and by the transaction manager
16151615
and returns a pointer to the saved plan. This gives you the
16161616
ability to reuse prepared plans in the subsequent invocations of
1617-
your procedure in the current session. You may save the pointer
1618-
returned in a local variable. Always check if this pointer is
1619-
<symbol>NULL</symbol> or not either when preparing a plan or using
1620-
an already prepared plan in <function>SPI_execute_plan</function>.
1617+
your procedure in the current session.
16211618
</para>
16221619
</refsect1>
16231620

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy