From: | Jonathan Pool <pool(at)utilika(dot)org> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Cc: | Susan Colowick <smc(at)utilika(dot)org> |
Subject: | Documentation bug: Chapter 35.4, paragraph 4 |
Date: | 2010-11-23 18:08:07 |
Message-ID: | 014DFDA2-CF76-4DB1-B3C2-0550BAE1A705@utilika.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-docs |
Chapter 35.4, paragraph 4, of the PostgreSQL 9.0.1 Documentation says:
Any collection of commands in the SQL language can be packaged together and defined as a function. Besides SELECT queries, the commands can include data modification queries (INSERT, UPDATE, and DELETE), as well as other SQL commands. (The only exception is that you cannot put BEGIN, COMMIT, ROLLBACK, or SAVEPOINT commands into a SQL function.)
This appears to be incorrect, in that attempting to include a VACUUM command in a query-language function elicits the following error message:
ERROR: VACUUM cannot be executed from a function or multi-command string
Thus, presumably "VACUUM" should be added to the list of exceptions.
ˉ
From | Date | Subject | |
---|---|---|---|
Next Message | abraham camacho | 2010-11-23 22:42:05 | BUG #5764: installation error (incomplete process) |
Previous Message | Tom Lane | 2010-11-23 15:29:43 | Re: BUG #5763: pg_hba.conf not honored |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2010-11-23 22:03:54 | pgsql: Add index entries for more functions |
Previous Message | Marti Raudsepp | 2010-11-19 08:35:11 | Re: [PATCH] Fix documentation about PL/Python exception handling |