Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
initdb(1)
Edit
PageHistory
Diff
Info
LikePages
INITDB !!!INITDB NAME SYNOPSIS DESCRIPTION ENVIRONMENT SEE ALSO ---- !!NAME initdb - create a new PostgreSQL database cluster !!SYNOPSIS __initdb --pgdata__ | __-D__ ''directory'' [[ __--username__ | __-U__ ''username'' ] [[ __--pwprompt__ | __-W__ ] [[ __--encoding__ | __-E__ ''encoding'' ] [[ __-L__ ''directory'' ] [[ __--noclean__ | __-n__ ] [[ __--debug__ | __-d__ ] !!DESCRIPTION __initdb__ creates a new PostgreSQL database cluster (or database system). A database cluster is a collection of databases that are managed by a single server instance. Creating a database system consists of creating the directories in which the database data will live, generating the shared catalog tables (tables that belong to the whole cluster rather than to any particular database), and creating the template1 database. When you create a new database, everything in the template1 database is copied. It contains catalog tables filled in for things like the built-in types. __initdb__ must be run as the user that will own the server process, because the server needs to have access to the files and directories that __initdb__ creates. Since the server may not be run as root, you must not run __initdb__ as root either. (It will in fact refuse to do so.) Although __initdb__ will attempt to create the specified data directory, often it won't have permission to do so, since the parent of the desired data directory is often a root-owned directory. To set up an arrangement like this, create an empty data directory as root, then use __chown__ to hand over ownership of that directory to the database user account, then __su__ to become the database user, and finally run __initdb__ as the database user. __OPTIONS__ __--pgdata=__''directory'' __-D__ ''directory'' This option specifies the directory where the database system should be stored. This is the only information required by __initdb__, but you can avoid writing it by setting the __PGDATA__ environment variable, which can be convenient since the database server (__postmaster__) can find the database directory later by the same variable. __--username=__''username'' __-U__ ''username'' Selects the user name of the database superuser. This defaults to the name of the effective user running __initdb__. It is really not important what the superuser's name is, but one might choose to keep the customary name ``postgres'', even if the operating system user's name is different. __--pwprompt__ __-W__ Makes __initdb__ prompt for a password to give the database superuser. If you don't plan on using password authentication, this is not important. Otherwise you won't be able to use password authentication until you have a password set up. __--encoding=__''encoding'' __-E__ ''encoding'' Selects the encoding of the template database. This will also be the default encoding of any database you create later, unless you override it there. To use the encoding feature, you must have enabled it at build time, at which time you also select the default for this option. Other, less commonly used, parameters are also available: __-L__ ''directory'' Specifies where __initdb__ should find its input files to initialize the database system. This is normally not necessary. You will be told if you need to specify their location explicitly. __--noclean__ __-n__ By default, when __initdb__ determines that an error prevented it from completely creating the database system, it removes any files it may have created before discovering that it can't finish the job. This option inhibits tidying-up and is thus useful for debugging. __--debug__ __-d__ Print debugging output from the bootstrap backend and a few other messages of lesser interest for the general public. The bootstrap backend is the program __initdb__ uses to create the catalog tables. This option generates a tremendous amount of extremely boring output. !!ENVIRONMENT __PGDATA__ Specifies the directory where the database system is to be stored; may be overridden using the __-D__ option. !!SEE ALSO postgres(1), postmaster(1), ''PostgreSQL Administrator's Guide'' ----
3 pages link to
initdb(1)
:
postmaster(1)
Man1i
postgres(1)
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
