Add new pages for programming languages and tcl shells.
&createdb;
+ &createlang;
&createuser;
&destroydb;
+ &destroylang;
&destroyuser;
&ecpgRef;
&pgAccess;
&pgDump;
&pgDumpall;
&psqlRef;
+ &pgTclSh;
+ &pgTkSh;
&vacuumdb;
-
+ id="sql-createtype-title">
CREATE TYPE
SQL - Language Statements
-
+ xreflabel="createdb">
PGREALM
environment variables will be passed on to
- and processed as described in .
+ and processed as described in
+ .
--- /dev/null
+
+
+
+
+
+
+ Application
+
+
+
+
+
+ Add a new programming language to a
Postgres database
+
+
+
+
+ 1999-08-05
+
+
+createlang [ langname ]
+createlang [ -h host ] [ -p port ]
+ [ langname ]
+
+
+
+
+ Inputs
+
+
createlang accepts the following command line arguments:
+
+
+
+ langname
+
+ Specifies the name of the backend programming language to be defined.
+
createlang will prompt for
+ langname
+ if it is not specified on the command line.
+
+
+
+
+
+
+
createlang also accepts
+ the following command line arguments for connection parameters:
+
+
+
+ -h host
+
+ Specifies the hostname of the machine on which the
+ is running. Defaults to using a local Unix domain socket
+ rather than an IP connection.
+
+
+
+
+
+ -p port
+
+ Specifies the Internet TCP/IP port or local Unix domain socket file
+ extension on which the
postmaster
+ is listening for connections. The port number defaults to 5432,
+ or the value of the PGPORT
+ environment variable (if set).
+
+
+
+
+
+
+
+
+
+
+ 1998-10-04
+
+
+ Outputs
+
+
createlang installs a new programming
+ language into a
Postgres server,
+ so has not explicit external output.
+
+
+
+
+
+
+ 1998-10-04
+
+
+ Description
+
+
+
createlang is a utility for adding a new
+ programming language to a
+
createlang currently accepts two
+ languages, plsql and pltcl.
+
+
+
+
+
+ Notes
+
+
+ See
+
+ for more details.
+
+
+
+
+
+ Usage
+
+ To install pltcl:
+
+% createlang pltcl
+
+
+
+
+
+
--- /dev/null
+
+
+
+
+
+
+ Application
+
+
+
+
+
+ Add a programming language to a
Postgres database
+
+
+
+
+ 1999-08-05
+
+
+destroylang [ langname ]
+destroylang [ -h host ] [ -p port ]
+ [ langname ]
+
+
+
+
+ Inputs
+
+
destroylang accepts the following command line arguments:
+
+
+
+ langname
+
+ Specifies the name of the backend programming language to be destroyed.
+
destroylang will prompt for
+ langname
+ if it is not specified on the command line.
+
+
+
+
+
+
+
destroylang also accepts
+ the following command line arguments for connection parameters:
+
+
+
+ -h host
+
+ Specifies the hostname of the machine on which the
+ is running. Defaults to using a local Unix domain socket
+ rather than an IP connection.
+
+
+
+
+
+ -p port
+
+ Specifies the Internet TCP/IP port or local Unix domain socket file
+ extension on which the
postmaster
+ is listening for connections. The port number defaults to 5432,
+ or the value of the PGPORT
+ environment variable (if set).
+
+
+
+
+
+
+
+
+
+
+ 1998-10-04
+
+
+ Outputs
+
+
destroylang removes an existing programming
+ language from a
Postgres server,
+ so has not explicit external output.
+
+
+
+
+
+
+ 1998-10-04
+
+
+ Description
+
+
+
destroylang is a utility for removing an
+ existing programming language from a
+
destroylang currently accepts two
+ languages, plsql and pltcl.
+
+
+
+
+
+ Notes
+
+
+ See
+
+ for more details.
+
+
+
+
+
+ Usage
+
+ To remove pltcl:
+
+% destroylang pltcl
+
+
+
+
+
+
-
+ xreflabel="drop_database">
DROP DATABASE
This query cannot be executed while connected to the target
database. It is usually preferable to use
- -title" endterm="app-destroydb-title">
+
instead.
Refer to
- -title" endterm="app-createdb-title"> and
- -title" endterm="sql-createdatabase-title">
+ and
+
for information on how to create a database.
- pgaccess-ref">
+ app-pgaccess-title">
Application
- 1999-05-19
+ 1999-08-03
pgaccess [ dbname ]
-
- 1999-05-19
-
Inputs
-
- 1999-05-19
-
Outputs
-
- 1999-05-19
-
Description
-
-
Editor's Note
- This should be transcribed from other pgaccess info. Volunteers?
-
-
+
pgaccess provides a graphical interface
+ where you
+ can manage your tables, edit them, define queries, sequences and
+ functions.
+
+
+ Another way of accessing
Postgres
+ through tcl is to use
+
+ or
+ .
+
+
+
+
+
+ Opens any database on a specified host at the specified port,
+ username and password.
+
+
+
+
+ Execute .
+
+
+
+
+ Saves preferences in ~/.pgaccessrc file.
+
+
+
+
+
+ For tables,
pgaccess can:
+
+
+
+ Open multiple tables for viewing, max n records (configurable).
+
+
+
+
+ Resize columns by dragging the vertical grid lines.
+
+
+
+
+ Wrap text in cells.
+
+
+
+
+ Dynamically adjust row height when editing.
+
+
+
+
+ Save table layout for every table.
+
+
+
+
+ Import/export to external files (SDF,CSV).
+
+
+
+
+ Use filter capabilities; enter filter like price>3.14.
+
+
+
+
+ Specify sort order; enter manually the sort field(s).
+
+
+
+
+ Edit in place; double click the text you want to change.
+
+
+
+
+ Delete records; point to the record, press Del key.
+
+
+
+
+ Add new records; save new row with right-button-click.
+
+
+
+
+ Create tables with an assistant.
+
+
+
+
+ Rename and delete (drop) tables.
+
+
+
+
+ Retrieve information on tables, including owner, field information, indices.
+
+
+
+
+
+ For queries,
pgaccess can:
+
+
+
+ Define, edit and store user defined queries.
+
+
+
+
+ Save view layouts.
+
+
+
+
+ Store queries as views.
+
+
+
+
+ Execute with optional user input parameters; e.g.
+select * from invoices where year=[parameter "Year of selection"]
+
+
+
+
+
+ View any select query result.
+
+
+
+
+ Run action queries (insert, update, delete).
+
+
+
+
+ Construct queries using a visual query builder
+ with drag & drop support, table aliasing.
+
+
+
+
+
+ For sequences,
pgaccess can:
+
+
+
+ Define new instances.
+
+
+
+
+ Inspect existing instances.
+
+
+
+
+ Delete.
+
+
+
+
+
+ For views,
pgaccess can:
+
+
+
+ Define them by saving queries as views.
+
+
+
+
+ View them, with filtering and sorting capabilities.
+
+
+
+
+ Design new views.
+
+
+
+
+ Delete (drop) existing views.
+
+
+
+
+
+ For functions,
pgaccess can:
+
+
+
+ Define.
+
+
+
+
+ Inspect.
+
+
+
+
+ Delete.
+
+
+
+
+
+ For reports,
pgaccess can:
+
+
+
+ Generate simple reports from a table (beta stage).
+
+
+
+
+ Change font, size and style of fields and labels.
+
+
+
+
+ Load and save reports from the database.
+
+
+
+
+ Preview tables, sample postscript print.
+
+
+
+
+
+ For forms,
pgaccess can:
+
+
+
+ Open user defined forms.
+
+
+
+
+ Use a form design module.
+
+
+
+
+ Access record sets using a query widget.
+
+
+
+
+
+ For scripts,
pgaccess can:
+
+
+
+ Define.
+
+
+
+
+ Modify.
+
+
+
+
+ Call user defined scripts.
+
+
+
- pgadmin-ref">
+ app-pgadmin-title">
Application
--- /dev/null
+
+
+
+
+
+
+ Application
+
+
+
+
+
+
Postgres TCL shell client
+
+
+
+
+ 1999-08-03
+
+
+pgtclsh [ dbname ]
+
+
+
+
+ Inputs
+
+
+
+
+ dbname
+
+ The name of an existing database to access.
+
+
+
+
+
+
+
+
+
+ Outputs
+
+
+
+
+
+
+
+ Description
+
+
pgtclsh provides a TCL shell interface
+
+
+ Another way of accessing
Postgres
+ through tcl is to use
+
+ or
+ .
+
+
+
+
+
--- /dev/null
+
+
+
+
+
+
+ Application
+
+
+
+
+
+
Postgres graphical TCL/TK shell
+
+
+
+
+ 1999-08-03
+
+
+pgtksh [ dbname ]
+
+
+
+
+ Inputs
+
+
+
+
+ dbname
+
+ The name of an existing database to access.
+
+
+
+
+
+
+
+
+
+ Outputs
+
+
+
+
+
+
+
+ Description
+
+
pgtksh provides a graphical TCL/TK shell interface
+
+
+ Another way of accessing
Postgres
+
+ or
+ .
+
+
+
+
+
Application
- id="postgres-ref">
+
Dates are accepted by the backend in a wide variety of formats,
and for input dates this switch mostly affects the interpretation
for ambiguous cases.
- See <xref linkend="datatype-title" endterm="datatype-title">
+ See <citetitle>The PostgreSQL User's Guide>
for more information.
- See also postmaster-ref" endterm="postmaster-ref">.
+ See also app-postmaster" endterm="app-postmaster-title">.
% setenv PGPORT 1234
% psql
- .
+
SELECT will return rows from one or more tables.
Candidates for selection are rows which satisfy the WHERE condition;
if WHERE is omitted, all rows are candidates.
- (See where-title" endterm="where-title">.)
+ (See sql-where" endterm="sql-where-title">.)
The GROUP BY clause allows a user to divide a table
conceptually into groups.
- (See group-by-title" endterm="group-by-title">.)
+ (See sql-groupby" endterm="sql-groupby-title">.)
The HAVING clause specifies a grouped table derived by the
elimination of groups from the result of the previously
specified clause.
- (See having-title" endterm="having-title">.)
+ (See sql-having" endterm="sql-having-title">.)
The ORDER BY clause allows a user to specify that he/she
wishes the rows sorted according to the ASCending or
DESCending mode operator.
- (See order-by-title" endterm="order-by-title">.)
+ (See sql-orderby-title" endterm="sql-orderby-title">.)
The UNION clause allows the result to be the collection of rows
returned by the queries involved.
- (See union-title" endterm="union-title">.)
+ (See sql-union" endterm="sql-union-title">.)
The INTERSECT give you the rows that are common to both queries.
- (See intersect-title" endterm="intersect-title">.)
+ (See sql-intersect" endterm="sql-intersect-title">.)
The EXCEPT give you the rows in the upper query not in the lower query.
- (See except-title" endterm="except-title">.)
+ (See sql-except" endterm="sql-except-title">.)
(See the GRANT/REVOKE statements).
- R2-SQL-WHERE-2">
+ SQL-WHERE">
1998-09-24
-
+
sql-where-title">
WHERE Clause
- R2-SQL-GROUPBY-2">
+ SQL-GROUPBY">
1998-09-24
-
group-by-title">
+
sql-groupby-title">
GROUP BY Clause
- R2-SQL-HAVING-2">
+ SQL-HAVING">
1998-09-24
-
+
sql-having-title">
HAVING Clause
- R2-SQL-ORDERBYCLAUSE-2">
+ SQL-ORDERBY">
1998-09-24
-
order-by-title">
+
sql-orderby-title">
ORDER BY Clause
- R2-SQL-UNION-2">
+ SQL-UNION">
1998-09-24
-
+
sql-union-title">
UNION Clause
- R2-SQL-INTERSECT-2">
+ SQL-INTERSECT">
1998-09-24
-
+
sql-intersect-title">
INTERSECT Clause
- R2-SQL-EXCEPT-2">
+ SQL-EXCEPT">
1998-09-24
-
+
sql-except-title">
EXCEPT Clause