From: Bruce Momjian <bruce@momjian.us>
Date: Mon, 8 Sep 1997 17:49:43 +0000 (+0000)
Subject: Manual page updates.
X-Git-Tag: REL6_2~233
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=4f523a6f92f98e1b10e84b2d5a58b0ac3e2f8c2a;p=postgresql

Manual page updates.
---

diff --git a/src/man/declare.l b/src/man/declare.l
new file mode 100644
index 0000000000..2d5d92e282
--- /dev/null
+++ b/src/man/declare.l
@@ -0,0 +1,39 @@
+.\" This is -*-nroff-*-
+.\" XXX standard disclaimer belongs here....
+.\" $Header: /cvsroot/pgsql/src/man/Attic/declare.l,v 1.1 1997/09/08 17:49:41 momjian Exp $
+.TH FETCH SQL 01/23/93 PostgreSQL PostgreSQL
+.SH NAME
+declere \(em declare a cursor
+.SH SYNOPSIS
+.nf
+\fBdeclare\fR [ \fBbinary\fR ] \fBcursor for\fR select statement
+.fi
+.SH DESCRIPTION
+.BR Declare
+allows a user to create cursors.
+Cursors are only available in transactions.
+.PP
+Normal cursors return data back in ASCII format.  Since data is stored
+natively in binary format, the system must do a conversion to produce
+the ASCII format.  In addition, ASCII formats are often larger in size
+than binary format.  Once the attributes come back in ASCII, often the
+client application then has to convert it to a binary format to
+manipulate it anyway.
+.PP
+\fBBinary\fR cursors give you back the data in the native binary
+representation.  Thus, binary cursors will tend to be a little faster
+since there's less overhead of conversion.
+.PP
+However, ASCII is architectural neutral whereas binary representation
+can differ between different machine architecture.  Thus, if your client
+machine uses a different representation than you server machine, getting
+back attributes in binary format is probably not what you want. Also, if
+your main purpose is displaying the data in ASCII, then getting it back
+in ASCII will save you some effort on the client side.
+.PP
+For an example, see the fetch(l) manual page.
+.SH "SEE ALSO"
+fetch(l),
+begin(l),
+end(l),
+select(l).
diff --git a/src/man/fetch.l b/src/man/fetch.l
index 8fe3737bec..b2550704d8 100644
--- a/src/man/fetch.l
+++ b/src/man/fetch.l
@@ -1,6 +1,6 @@
 .\" This is -*-nroff-*-
 .\" XXX standard disclaimer belongs here....
-.\" $Header: /cvsroot/pgsql/src/man/Attic/fetch.l,v 1.3 1997/03/01 15:26:42 momjian Exp $
+.\" $Header: /cvsroot/pgsql/src/man/Attic/fetch.l,v 1.4 1997/09/08 17:49:41 momjian Exp $
 .TH FETCH SQL 01/23/93 PostgreSQL PostgreSQL
 .SH NAME
 fetch \(em fetch instance(s) from a cursor
@@ -64,7 +64,3 @@ end(l),
 close(l),
 move(l),
 select(l).
-.SH BUGS
-Currently, the smallest transaction in Postgres is a single SQL
-command.  It should be possible for a single fetch to be a
-transaction.
diff --git a/src/man/vacuum.l b/src/man/vacuum.l
index 312e1728eb..5557060e85 100644
--- a/src/man/vacuum.l
+++ b/src/man/vacuum.l
@@ -1,6 +1,6 @@
 .\" This is -*-nroff-*-
 .\" XXX standard disclaimer belongs here....
-.\" $Header: /cvsroot/pgsql/src/man/Attic/vacuum.l,v 1.4 1997/05/13 04:41:54 momjian Exp $
+.\" $Header: /cvsroot/pgsql/src/man/Attic/vacuum.l,v 1.5 1997/09/08 17:49:43 momjian Exp $
 .TH VACUUM SQL 11/05/95 PostgreSQL PostgreSQL
 .SH NAME
 vacuum \(em vacuum a database
@@ -40,5 +40,11 @@ choices in planning user queries.
 .PP
 The purge(l) command can be used to control the archive retention
 characteristics of a given table.
+.PP
+If the server crashes during a vacuum command, chances are it will leave
+a lock file hanging around.  Attempts to re-run the vacuum command
+result in an error message about the creation of a lock file.  If you
+are sure vacuum is not running, remove the pg_vlock file in your
+database directory(i.e. data/base/dbname/pg_vlock).
 .SH "SEE ALSO"
 purge(l).