@@ -143,6 +143,7 @@ <H2 align="center">Operational Questions</H2>
143143 from a function?< BR >
144144< A href ="#4.26 "> 4.26</ A > ) Why can't I reliably create/drop
145145 temporary tables in PL/PgSQL functions?< BR >
146+ < A href ="#4.27 "> 4.27</ A > ) What replication options are available?< BR >
146147
147148
148149< H2 align ="center "> Extending PostgreSQL</ H2 >
@@ -1346,12 +1347,14 @@ <H4><A name="4.23">4.23</A>) How do I perform an outer join?</H4>
13461347< H4 > < A name ="4.24 "> 4.24</ A > ) How do I perform queries using
13471348 multiple databases?</ H4 >
13481349
1349- < P > There is no way to queryany databaseexcept the current one.
1350+ < P > There is no way to querya databaseother than the current one.
13501351 Because PostgreSQL loads database-specific system catalogs, it is
13511352 uncertain how a cross-database query should even behave.</ P >
13521353
1353- < P > Of course, a client can make simultaneous connections to
1354- different databases and merge the information that way.</ P >
1354+ < P > < I > /contrib/dblink</ I > allows cross-database queries using
1355+ function calls. Of course, a client can make simultaneous
1356+ connections to different databases and merge the results on the
1357+ client side.</ P >
13551358
13561359< H4 > < A name ="4.25 "> 4.25</ A > ) How do I return multiple rows or
13571360 columns from a function?</ H4 >
@@ -1364,13 +1367,19 @@ <H4><A name="4.25">4.25</A>) How do I return multiple rows or
13641367
13651368< H4 > < A name ="4.26 "> 4.26</ A > ) Why can't I reliably create/drop
13661369 temporary tables in PL/PgSQL functions?</ H4 >
1367- PL/PgSQL caches function contents, and an unfortunate side effect
1370+ < P > PL/PgSQL caches function contents, and an unfortunate side effect
13681371 is that if a PL/PgSQL function accesses a temporary table, and that
13691372 table is later dropped and recreated, and the function called
13701373 again, the function will fail because the cached function contents
13711374 still point to the old temporary table. The solution is to use
13721375< SMALL > EXECUTE</ SMALL > for temporary table access in PL/PgSQL. This
1373- will cause the query to be reparsed every time.
1376+ will cause the query to be reparsed every time.</ P >
1377+
1378+ < H4 > < A name ="4.27 "> 4.27</ A > ) What replication options are available?
1379+ </ H4 >
1380+ < P > There are several master/slave replication solutions available.
1381+ These allow only one server to make database changes and the slave
1382+ merely allow database reading.
13741383
13751384< HR >
13761385