From c86fac278720a43548ffa0cfabaa069461da6d16 Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Mon, 10 Jun 2002 20:45:07 +0000 Subject: [PATCH] Fix link. --- doc/FAQ | 2 +- doc/src/FAQ/FAQ.html | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/FAQ b/doc/FAQ index 165bc94d4e..3a63f7f38d 100644 --- a/doc/FAQ +++ b/doc/FAQ @@ -1,7 +1,7 @@ Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Mon Jun 10 15:49:44 EDT 2002 + Last updated: Mon Jun 10 16:44:55 EDT 2002 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html index 09faa581ff..d40aa45f36 100644 --- a/doc/src/FAQ/FAQ.html +++ b/doc/src/FAQ/FAQ.html @@ -14,7 +14,7 @@ alink="#0000ff">

Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Mon Jun 10 15:49:44 EDT 2002

+

Last updated: Mon Jun 10 16:44:55 EDT 2002

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -1317,7 +1317,7 @@ BYTEA bytea variable-length byte array (null-byte safe) http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html, section 23.7.3.3.

-

4.26) Why can't I reliably create/drop +

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 is that if a PL/PgSQL function accesses a temporary table, and that -- 2.11.0