diff --git a/reference/pgsql/functions/pg-fetch-all.xml b/reference/pgsql/functions/pg-fetch-all.xml
new file mode 100644
index 0000000000..3a32d73dc3
--- /dev/null
+++ b/reference/pgsql/functions/pg-fetch-all.xml
@@ -0,0 +1,76 @@
+
+
+
+
+
+ pg_fetch_all
+ Fetch a row as an array
+
+
+ Description
+
+ arraypg_fetch_all
+ resourceresult
+ introw
+
+
+ pg_fetch_all returns an array that
+ contains all row (tuples/records) in result resource. It returns
+ &false;, if there are no more rows.
+
+
+ See also pg_fetch_row,
+ pg_fetch_array,
+ pg_fetch_object and
+ pg_fetch_result.
+
+
+
+ PostgreSQL fetch array
+
+
+]]>
+
+
+
+
+
+
+
diff --git a/reference/pgsql/functions/pg-fetch-assoc.xml b/reference/pgsql/functions/pg-fetch-assoc.xml
new file mode 100644
index 0000000000..232b87ea59
--- /dev/null
+++ b/reference/pgsql/functions/pg-fetch-assoc.xml
@@ -0,0 +1,90 @@
+
+
+
+
+
+ pg_fetch_assoc
+ Fetch a row as an array
+
+
+ Description
+
+ arraypg_fetch_assoc
+ resourceresult
+ introw
+
+
+ pg_fetch_assoc returns an associative array that
+ corresponds to the fetched row (tuples/records). It returns
+ &false;, if there are no more rows.
+
+
+ pg_fetch_assoc is an extended version of
+ pg_fetch_row. In addition to storing the
+ data in the numeric indices (field index) to the result array, it
+ also stores the data in associative indices (field name) by
+ default.
+
+
+ row is row (record) number to be
+ retrieved. First row is 0.
+
+
+ pg_fetch_assoc is NOT significantly
+ slower than using pg_fetch_row, while it
+ provides a significant ease of use.
+
+
+ See also pg_fetch_row,
+ pg_fetch_array,
+ pg_fetch_object and
+ pg_fetch_result.
+
+
+
+ PostgreSQL fetch array
+
+
+]]>
+
+
+
+
+
+
+
diff --git a/reference/pgsql/functions/pg-result-seek.xml b/reference/pgsql/functions/pg-result-seek.xml
new file mode 100644
index 0000000000..1de95aa766
--- /dev/null
+++ b/reference/pgsql/functions/pg-result-seek.xml
@@ -0,0 +1,49 @@
+
+
+
+
+
+ pg_result_seek
+ Set internal row offset in result resource
+
+
+ Description
+
+ arraypg_result_seek
+ resourceresult
+ intoffset
+
+
+ pg_result_seek set internal row offset in
+ reuslt resource. It returns &false;, if there is error.
+
+
+ See also pg_fetch_row,
+ pg_fetch_assoc,
+ pg_fetch_array,
+ pg_fetch_object and
+ pg_fetch_result.
+
+
+
+
+
diff --git a/reference/pgsql/functions/pg-unescape-bytea.xml b/reference/pgsql/functions/pg-unescape-bytea.xml
new file mode 100644
index 0000000000..4e8ac9740d
--- /dev/null
+++ b/reference/pgsql/functions/pg-unescape-bytea.xml
@@ -0,0 +1,63 @@
+
+
+
+
+
+ pg_unescape_bytea
+
+ Escape binary for bytea type
+
+
+
+ Description
+
+ stringpg_unescape_bytea
+ stringdata
+
+
+ pg_unescape_bytea unescapes string from
+ bytea datatype. It returns unescaped string (binary).
+
+
+
+ When you SELECT bytea type, PostgreSQL returns octal byte value
+ prefixed by \ (e.g. \032). Users are supposed to convert back to
+ binary format by yourself.
+
+
+ This function requires PostgreSQL 7.2 or later. With PostgreSQL
+ 7.2.0 and 7.2.1, bytea type must be casted when you enable
+ multi-byte support. i.e. INSERT INTO test_table (image)
+ VALUES ('$image_escaped'::bytea); PostgreSQL 7.2.2 or
+ later does not need cast. Exception is when client and backend
+ character encoding does not match, there may be multi-byte
+ stream error. User must cast to bytea to avoid this error.
+
+
+
+ See also pg_escape_bytea and
+ pg_escape_string
+
+
+
+
+