From 6a7bb0afbcab1ac3f1e9bbcb536bc7865f4503e6 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Fri, 11 Oct 2002 04:12:14 +0000 Subject: Prevent tv_sec from becoming negative in connection timeout code. --- doc/src/FAQ/FAQ.html | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 54587662260..a78c4167896 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -143,6 +143,7 @@ from a function?
4.26) Why can't I reliably create/drop temporary tables in PL/PgSQL functions?
+ 4.27) What replication options are available?

Extending PostgreSQL

@@ -1346,12 +1347,14 @@ BYTEA bytea variable-length byte array (null-byte safe)

4.24) How do I perform queries using multiple databases?

-

There is no way to query any database except the current one. +

There is no way to query a database other than the current one. Because PostgreSQL loads database-specific system catalogs, it is uncertain how a cross-database query should even behave.

-

Of course, a client can make simultaneous connections to - different databases and merge the information that way.

+

/contrib/dblink allows cross-database queries using + function calls. Of course, a client can make simultaneous + connections to different databases and merge the results on the + client side.

4.25) How do I return multiple rows or columns from a function?

@@ -1364,13 +1367,19 @@ BYTEA bytea variable-length byte array (null-byte safe)

4.26) Why can't I reliably create/drop temporary tables in PL/PgSQL functions?

- PL/PgSQL caches function contents, and an unfortunate side effect +

PL/PgSQL caches function contents, 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 the old temporary table. The solution is to use EXECUTE for temporary table access in PL/PgSQL. This - will cause the query to be reparsed every time. + will cause the query to be reparsed every time.

+ +

4.27) What replication options are available? +

+

There are several master/slave replication solutions available. + These allow only one server to make database changes and the slave + merely allow database reading.

-- cgit v1.2.3