create database - Docs search results , p.11
Documentation >> Postgres Pro Standard 9.6
14.4. Populating a Database
recreate the indexes. Of course, the database performance for other users might suffer during the time
Documentation >> Postgres Pro Standard 9.6
8.1. Numeric Types
creating unique identifier columns (similar to the AUTO_INCREMENT property supported by some other databases
Documentation >> Postgres Pro Standard 9.6
48.55. pg_type
created for each table in the database, to represent the row structure of the table
Documentation >> Postgres Pro Standard 9.6
14.5. Non-Durable Settings
database software; only abrupt operating system stoppage creates a risk of data loss or corruption
Documentation >> Postgres Pro Standard 9.6
34.4. Query Language (SQL) Functions
creates a need for precautions when calling functions in databases where some users mistrust other
Documentation >> Postgres Pro Standard 9.6
pg_standby
creation of a “ warm standby ” database server. It is designed to be a production-ready
Documentation >> Postgres Pro Standard 9.6
25.2. Log-Shipping Standby Servers
create the primary and standby servers so that they are as similar as possible, at least from the perspective of the database
Documentation >> Postgres Pro Standard 9.6
psql
database roles. (Since the concepts of “ users ” and “ groups ” have been unified into “ roles ” , this command is now equivalent to \du .) By default, only user-created
Documentation >> Postgres Pro Standard 9.6
30.6. Canceling Queries in Progress
Creates a data structure containing the information needed to cancel a command issued through a particular database
Documentation >> Postgres Pro Standard 9.6
5.4. System Columns
database-wide identifier. Of course, the tables in question must be created WITH OIDS . As of PostgreSQL
Documentation >> Postgres Pro Standard 9.6
16.3. Installing Additional Supplied Modules
database in order to use them. In most cases, you only need to issue the CREATE
Documentation >> Postgres Pro Standard 9.6
CREATE FOREIGN TABLE
creates a new foreign table in the current database. The table will be owned by the user
Documentation >> Postgres Pro Standard 9.6
18.3. Connections and Authentication
database user names. It is off by default. This parameter can only be set in the postgresql.conf file or on the server command line. If this is on, you should create
Documentation >> Postgres Pro Standard 9.6
ALTER INDEX
CREATE privilege on the new tablespace. All indexes in the current database in a tablespace
Documentation >> Postgres Pro Standard 9.6
E.48. Release 9.6.9
creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database