summaryrefslogtreecommitdiff
path: root/doc/FAQ
diff options
context:
space:
mode:
authorBruce Momjian2005-02-01 02:40:50 +0000
committerBruce Momjian2005-02-01 02:40:50 +0000
commit4f63cc6a30357d1780f73b056872fe1726c4e9e5 (patch)
tree0c1d8103c04bd1d3363a4dfc1b9d7028f7c40c0e /doc/FAQ
parent3c16965995223b0ae66e027389863448ac0bade7 (diff)
Final FAQ cleanups to remove information about very old releases.
Diffstat (limited to 'doc/FAQ')
-rw-r--r--doc/FAQ13
1 files changed, 6 insertions, 7 deletions
diff --git a/doc/FAQ b/doc/FAQ
index 4c03f78c24e..58842e75b90 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Mon Jan 31 21:35:15 EST 2005
+ Last updated: Mon Jan 31 21:40:28 EST 2005
Current maintainer: Bruce Momjian ([email protected])
@@ -808,18 +808,18 @@
uncertain how a cross-database query should even behave.
contrib/dblink allows cross-database queries using function calls. Of
- course, a client can make simultaneous connections to different
+ course, a client can also make simultaneous connections to different
databases and merge the results on the client side.
4.19) How do I return multiple rows or columns from a function?
- In 7.3, you can easily return multiple rows or columns from a
- function, http://techdocs.postgresql.org/guides/SetReturningFunctions.
+ It is easy using set-returning functions,
+ http://techdocs.postgresql.org/guides/SetReturningFunctions.
4.20) Why can't I reliably create/drop temporary tables in PL/PgSQL
functions?
- PL/PgSQL caches function contents, and an unfortunate side effect is
+ PL/PgSQL caches function scripts, and an unfortunate side effect is
that if a PL/PgSQL function accesses a temporary table, and that table
is later dropped and recreated, and the function called again, the
function will fail because the cached function contents still point to
@@ -838,8 +838,7 @@
possible to use a third-party encrypted transport, such as stunnel
or ssh, rather than PostgreSQL's native SSL connections.)
* Database user passwords are automatically encrypted when stored in
- version 7.3. In previous versions, you must enable the option
- PASSWORD_ENCRYPTION in postgresql.conf.
+ the system tables.
* The server can run using an encrypted file system.
_________________________________________________________________