- required.
+
+ &intro;
+ &history;
+]]>
- After you have worked through this tutorial you might want to move on to
- reading &cite-user; to gain a more formal knowledge of the SQL language,
- or &cite-programmer; for information about developing applications for
-
+
+
What's In This Book
- We hope you have a pleasant experience with
-
-
+ Welcome to
PostgreSQL and the
+ PostgreSQL Tutorial. The following few
+ chapters are intended to give a simple introduction to
+
PostgreSQL, relational database
+ concepts, and the SQL language to those who are new to any one of
+ these aspects. We only assume some general knowledge about how to
+ use computers. No particular Unix or programming experience is
+ required. This book is mainly intended to give you a hands-on
+ experience with important aspects of the PostgreSQL system. It
+ makes no attempt to be a complete or thorough treatment of the
+ topics it covers.
+
+
+ After you have worked through this tutorial you might want to move
+ on to reading the &cite-user; to gain a more formal knowledge of
+ the SQL language, or the &cite-programmer; for information about
+ developing applications for
PostgreSQL.
+ Those who set up and manage their own server should also read the
+ &cite-admin;.
+
+
- &intro;
+ &info;
+ ¬ation;
+ &problems;
]]>
+
+
&start;
&query;
&advanced;
This chapter describes how to create and manage users and introduces
the privilege system. More information about the various types of
- database objects and the effects of privileges can be found in
+ database objects and the effects of privileges can be found in the
&cite-user;.
&legal;
- &intro;
+
Preface
+ &intro;
+ &history;
+
+
+
What's In This Book
+
+ This book describes the use of the SQL language in PostgreSQL. We
+ start with describing the general syntax of SQL, then explain how
+ to create the structures to hold data, how to populate the
+ database, and how to query it. The middle part lists the
+ available data types and functions for use in SQL data commands.
+ The rest of the book treats several aspects that are important for
+ tuning a database for optimial performance.
+
+
+ The information in this book is arranged so that a novice user can
+ follow it start to end to gain a full understanding of the topics
+ without having to refer forward too many times. The chapters are
+ intended to be self-contained, so that advanced users can read the
+ chapters individually as they choose. The information in this
+ book is presented in a narrative fashion in topical units.
+ Readers looking for a complete description of a particular command
+ should look into the &cite-reference;.
+
+
+ Readers of this book should know how to connect to a PostgreSQL
+ database and issue SQL commands. Readers that are unfamiliar with
+ these issues are encouraged to read the &cite-tutorial; first. SQL
+ commands are typically entered using the PostgreSQL interactive
+ terminal
psql, but other programs that
+ have similar functionality can be used as well.
+
+
+ This book covers
PostgreSQL &version;+ only. For information on other versions, please read the
+ documentation that accompanies that release.
+
+
+
+ &info;
+ ¬ation;
+ &problems;
+
+
&syntax;
&ddl;
&dml;
+++ /dev/null
-
-
-
-
Y2K Statement
-
-
-
Author
-
- Written by Thomas Lockhart
- on 1998-10-22. Updated 2000-03-31.
-
-
-
- The
PostgreSQL Global Development Group provides
- the
PostgreSQL software code tree as a public service,
- without warranty and without liability for its behavior or performance.
- However, at the time of writing:
-
-
-
-
- The author of this statement, a volunteer on the
- support team since November, 1996, is not aware of
- any problems in the
PostgreSQL code base related
- to time transitions around Jan 1, 2000 (Y2K).
-
-
-
-
- The author of this statement is not aware of any reports of Y2K problems
- uncovered in regression testing
- or in other field use of recent or current versions
- of
PostgreSQL. We might have expected
- to hear about problems if they existed, given the installed base and
- the active participation of users on the support mailing lists.
-
-
-
-
- To the best of the author's knowledge, the
- makes about dates specified with a two-digit year
- are documented in the current User's Guide
- in the chapter on data types.
- For two-digit years, the significant transition year is 1970, not 2000;
- e.g. 70-01-01 is interpreted as 1970-01-01,
- whereas 69-01-01 is interpreted as 2069-01-01.
-
-
-
-
- Any Y2K problems in the underlying OS related to obtaining the
- current time
may propagate into apparent Y2K problems in
-
-
-
-
- Refer to
- and
- for further discussion of Y2K issues, particularly
- as it relates to open source, no fee software.
-
-
-
-
-
projects / postgresql.git / commitdiff