|
|
|
@ -14,7 +14,7 @@ |
|
|
|
|
alink="#0000ff"> |
|
|
|
|
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Mon Jun 10 15:49:44 EDT 2002</P> |
|
|
|
|
<P>Last updated: Mon Jun 10 16:44:55 EDT 2002</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> |
|
|
|
@ -1317,7 +1317,7 @@ BYTEA bytea variable-length byte array (null-byte safe) |
|
|
|
|
http://developer.postgresql.org/docs/postgres/plpgsql-cursors.html,</A> |
|
|
|
|
section 23.7.3.3.</P> |
|
|
|
|
|
|
|
|
|
<H4><A href="#4.26">4.26</A>) Why can't I reliably create/drop |
|
|
|
|
<H4><A href="4.26">4.26</A>) Why can't I reliably create/drop |
|
|
|
|
temporary tables in PL/PgSQL functions?</H4> |
|
|
|
|
PL/PgSQL caches function contents, and an unfortunate side effect |
|
|
|
|
is that if a PL/PgSQL function accesses a temporary table, and that |
|
|
|
|