Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit4f63cc6

Browse files
committed
Final FAQ cleanups to remove information about very old releases.
1 parent3c16965 commit4f63cc6

File tree

2 files changed

+15
-17
lines changed

2 files changed

+15
-17
lines changed

‎doc/FAQ

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
Frequently Asked Questions (FAQ) for PostgreSQL
33

4-
Last updated: Mon Jan 31 21:35:15 EST 2005
4+
Last updated: Mon Jan 31 21:40:28 EST 2005
55

66
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
77

@@ -808,18 +808,18 @@
808808
uncertain how a cross-database query should even behave.
809809

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

814814
4.19) How do I return multiple rows or columns from a function?
815815

816-
In 7.3, you can easily return multiple rows or columns from a
817-
function,http://techdocs.postgresql.org/guides/SetReturningFunctions.
816+
It is easy using set-returning functions,
817+
http://techdocs.postgresql.org/guides/SetReturningFunctions.
818818

819819
4.20) Why can't I reliably create/drop temporary tables in PL/PgSQL
820820
functions?
821821

822-
PL/PgSQL caches functioncontents, and an unfortunate side effect is
822+
PL/PgSQL caches functionscripts, and an unfortunate side effect is
823823
that if a PL/PgSQL function accesses a temporary table, and that table
824824
is later dropped and recreated, and the function called again, the
825825
function will fail because the cached function contents still point to
@@ -838,8 +838,7 @@
838838
possible to use a third-party encrypted transport, such as stunnel
839839
or ssh, rather than PostgreSQL's native SSL connections.)
840840
* Database user passwords are automatically encrypted when stored in
841-
version 7.3. In previous versions, you must enable the option
842-
PASSWORD_ENCRYPTION in postgresql.conf.
841+
the system tables.
843842
* The server can run using an encrypted file system.
844843
_________________________________________________________________
845844

‎doc/src/FAQ/FAQ.html

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@
1010
alink="#0000ff">
1111
<H1>Frequently Asked Questions (FAQ) for PostgreSQL</H1>
1212

13-
<P>Last updated: Mon Jan 31 21:35:15 EST 2005</P>
13+
<P>Last updated: Mon Jan 31 21:40:28 EST 2005</P>
1414

1515
<P>Current maintainer: Bruce Momjian (<Ahref=
1616
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)
@@ -1040,25 +1040,25 @@ <H4><A name="4.18">4.18</A>) How do I perform queries using
10401040
uncertain how a cross-database query should even behave.</P>
10411041

10421042
<P><I>contrib/dblink</I> allows cross-database queries using
1043-
function calls. Of course, a client can make simultaneous
1043+
function calls. Of course, a client canalsomake simultaneous
10441044
connections to different databases and merge the results on the
10451045
client side.</P>
10461046

10471047
<H4><Aname="4.19">4.19</A>) How do I return multiple rows or
10481048
columns from a function?</H4>
10491049

1050-
<P>In 7.3, you can easily return multiple rows or columns from a
1051-
function,
1050+
<P>It is easy using set-returning functions,
10521051
<ahref="http://techdocs.postgresql.org/guides/SetReturningFunctions">
10531052
http://techdocs.postgresql.org/guides/SetReturningFunctions</a>.
10541053

10551054
<H4><Aname="4.20">4.20</A>) Why can't I reliably create/drop
10561055
temporary tables in PL/PgSQL functions?</H4>
1057-
<P>PL/PgSQL caches function contents, and an unfortunate side effect
1056+
1057+
<P>PL/PgSQL caches function scripts, and an unfortunate side effect
10581058
is that if a PL/PgSQL function accesses a temporary table, and that
1059-
table is later dropped and recreated, and the function called
1060-
again,the function will fail because the cached function contents
1061-
stillpoint to the old temporary table. The solution is to use
1059+
table is later dropped and recreated, and the function called again,
1060+
the function will fail because the cached function contents still
1061+
point to the old temporary table. The solution is to use
10621062
<SMALL>EXECUTE</SMALL> for temporary table access in PL/PgSQL. This
10631063
will cause the query to be reparsed every time.</P>
10641064

@@ -1075,8 +1075,7 @@ <H4><A name="4.21">4.21</A>) What encryption options are available?
10751075
encrypted transport, such as stunnel or ssh, rather than PostgreSQL's
10761076
native SSL connections.)
10771077
<LI>Database user passwords are automatically encrypted when stored in
1078-
version 7.3. In previous versions, you must enable the option
1079-
<I>PASSWORD_ENCRYPTION</I> in<I>postgresql.conf</I>.</LI>
1078+
the system tables.</LI>
10801079
<LI>The server can run using an encrypted file system.</LI>
10811080
</UL>
10821081

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp