| From: | Brook Milligan <brook(at)biology(dot)nmsu(dot)edu> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | undocumented parts of SPI |
| Date: | 2001-02-14 23:18:57 |
| Message-ID: | 200102142318.QAA08020@biology.nmsu.edu |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I'm trying to figure out the SPI and need a bit of help, because the
docs do not mention (that I can find) some parts of the interface.
- SPI_exec(char * sql, int count): this function seems to execute the
query. Is the `count' parameter the maximum number of tuples to
return? Does count=0 imply return everything? Return value are the
SPI_* flags defined in spi.h?
- SPI_processed: number of tuples processed during execution of
SPI_exec? Does this equate to N in the INSERT/DELETE/UPDATE N
messages that are emitted by psql?
- Are there any restrictions on what types of queries may be executed
by a trigger using SPI_exec?
Thanks for the help.
Cheers,
Brook
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2001-02-15 01:41:44 | Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database? |
| Previous Message | Tom Lane | 2001-02-14 23:15:04 | Re: Shouldn't non-MULTIBYTE backend refuse to start in MB database? |