database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-12-21 05:21:08 +03:00
Code Activity

Consistenly use colons before '<programlisting>' blocks, where

Browse Source 
appropriate.
This commit is contained in:
Bruce Momjian
2007-02-01 00:28:19 +00:00
parent e81c138e18
commit 09a9f10e7f
62 changed files with 402 additions and 405 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/spi.sgml
View File

@@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.50 2007/01/31 20:56:19 momjian Exp $ -->
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.51 2007/02/01 00:28:18 momjian Exp $ -->
<chapter id="spi">
<title>Server Programming Interface</title>
@@ -313,7 +313,7 @@ int SPI_execute(const char * <parameter>command</parameter>, bool <parameter>rea
for all rows that it applies to. If <parameter>count</parameter>
is greater than 0, then the number of rows for which the command
will be executed is restricted (much like a
<literal>LIMIT</literal> clause). For example,
<literal>LIMIT</literal> clause). For example:
<programlisting>
SPI_execute("INSERT INTO foo SELECT * FROM bar", false, 5);
</programlisting>
@@ -2931,7 +2931,7 @@ int SPI_freeplan(void *<parameter>plan</parameter>)
<para>
During the execution of an SQL command, any data changes made by
the command are invisible to the command itself. For
example, in
example, in:
<programlisting>
INSERT INTO a SELECT * FROM a;
</programlisting>